Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Poet Upload & Persistence #14

Closed
3 of 6 tasks
asmr-hex opened this issue Feb 18, 2018 · 0 comments
Closed
3 of 6 tasks

Implement Poet Upload & Persistence #14

asmr-hex opened this issue Feb 18, 2018 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@asmr-hex
Copy link
Owner

asmr-hex commented Feb 18, 2018

Overview

when creating poets, a user should be able to upload an executable file and an optional parameters file

Requirements

  • uploaded files should be stored on the filesystem

TODO

@asmr-hex asmr-hex self-assigned this Feb 18, 2018
@asmr-hex asmr-hex added the enhancement New feature or request label Feb 18, 2018
asmr-hex pushed a commit that referenced this issue Feb 22, 2018
poet files on host fs, included sample data dir with sample
program/parameters files, added constants for file upload API, filled
in the body of CreatPoet in API handlers, created Users and Poets
Tables on Platform setup, added Language field/column to Poets data
model

TODOS:
* need to return HTTP responses to users in CreatePoet handler
* need to write unit tests for Creat Poet handler
* Must implement User creation/auth/session stuff (idk???) in order to
  properly create a poet (since the poets table in Postgres references
  UUIDs within the users table)
* possibly refactor the id arg in poet.Create.
asmr-hex pushed a commit that referenced this issue Feb 22, 2018
in-memory session token cache, modified user table to include hashed
password and salt, implement session methods for correlating userIds
to session tokens and vice versa

❀‿❀ -- yay!!

(づ。◕‿‿◕。)づ -- wheeeeee

╰(◡‿◡✿╰) -- whoooooo

TODOS:
* use CookieJar instead of Cookie?
* standardize form vs. data for requests
* implement session token expiration policy goroutine
* actually send responses to clients (send session token cookie as
  well)
* write unit test for all of this ;___;
asmr-hex pushed a commit that referenced this issue Feb 23, 2018
Major Changes:
* add http responses for login, register, and create poet
* send session token in login response
* implemement session token background sweeper

Notes:
* tests are currently broken (1 server test)
* token timeout duration is hard-coded, move to config

( ˘ ³˘)♥ ( ˘ ³˘)♥ ( ˘ ³˘)♥ ( ˘ ³˘)♥ ( ˘ ³˘)♥
asmr-hex pushed a commit that referenced this issue Feb 25, 2018
Major Changes:
* add create, read, update, delete validation for poets
* implement name regexp validator (supports unicode)
* unit tests for name regexp validator

TODO:
* validate that poet can only be created/modified/deleted by designer
* test coverage for poet validator function
@asmr-hex asmr-hex mentioned this issue Mar 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant