ajm188 / fugl Goto Github PK

Endpoint to check if a username is taken. There may be some other form validation endpoints, but that is the first one I thought of.

GET request with the project id and get back the s that belong to it.
This is supported Page Plugins and Post Plugins.

literally every URL (except "/", "/login", "/logout", "/register") begins with "/project".

We could remove this and do our routing more similarly to GitHub. The only caveat I can see is that we would have to prevent users from naming themselves "login", "logout" or "register."

^

Needs to be available endpoint for projects since (owner, project) needs to be unique. Didn't think of it till I started hooking it up

I need to figure out what this key is for before I blindly turn on travis builds.

Issue for discussion on what I've been working on. Way I see it, we need the following endpoints (all of which require auth):

• list projects owned by user
• list projects shared with user
• list projects owned or shared with user
• show a single project
  • user must be able to view project
• update a project
  • user must be able to edit project
• update sharing settings on a project
  • user must be owner
• delete a project
  • user must be owner

I may just be missing it, but I don't think there is a way to list all the s for a project.

See fugl/main/views/root.py, line 9.

1. There is no longer any pelican-themes directory with submodules. It's all part of the themes/ directory.
2. python manage.py populate takes an additional argument that isn't mentioned. Instead, you should run it from the root like this python fug/manage.py populate themes/.
3. You need to run a command like this: sudo -u postgres initdb --locale $LANG -E UTF8 -D '/var/lib/postgres/data' before you run the CREATE DATABASE command.
4. Before running the populate script, you should run make migrate so that the database gets initialized.

how did i forget about this one

Seems to point to https://jpcjr.github.io/fugl/doc.