SPA & REST template using Prologue, Norm and Karax

The template is not ready yet, but you can follow all changes on changelog

• Nim (Programming language)
• Norm (ORM)
• Prologue (Backend framework)
• Karax (Frontend framework)

• User manipulation in a SQLite DB
• .env configs
• REST API
• SPA
• 100% in Nim
• Boilerplate free
• A lot of abstractions

The API understands the body type as JSON, url-encoded and forms. Just specify the Content-Type

Example:

POST /api/signin HTTP/1.1
Content-Type: application/json

{
  "username": "user",
  "password": "pass"
}

Example:

POST /api/signup HTTP/1.1
Content-Type: application/json

{
  "username": "user",
  "email": "user@localhost",
  "password": "pass",
}

Example:

POST /api/logout HTTP/1.1
Cookie: session=<LOGGED SESSION>

Example:

POST /api/delUser HTTP/1.1
Cookie: session=<LOGGED SESSION>

Example:

POST /api/activate HTTP/1.1
Content-Type: application/json

{
  "username": "user",
  "password": "pass",
  "code": "verification code",
}

Example:

GET /api/resend/activation HTTP/1.1

Admin

Example:

POST /api/admin/getUser HTTP/1.1
Content-Type: application/json
Cookie: session=<ADMIN SESSION>

{
  "_username": "user" // Get using username
  // "_email": "user@localhost" // Get using email
}

Example: (can edit multiple fields at same time too)

POST /api/admin/getUser HTTP/1.1
Content-Type: application/json
Cookie: session=<ADMIN SESSION>

{
  "_username": "admin", // Edit using username
  // "_email": "admin@localhost", // Edit using email
  "rank": "urUser" // Can edit almost any field, in this case, we are removing admin privileges
}

Example:

POST /api/admin/getUser HTTP/1.1
Content-Type: application/json
Cookie: session=<ADMIN SESSION>

{
  "_username": "user", // Delete using username
  // "_email": "user@localhost", // Delete using email
}

Any API request can be made with application/json, application/x-www-form-urlencoded and multipart/form-data content types, just specify the Content-Type header

1. Uncomment .env in .gitignore
2. Replace all respSpa to your project name (including files/dirs names and inside files)
3. Change the secretKey in .env
4. Change the version, description and author in nimble file - Don't forget the credits ;)

• In production disable the debug in .env

• All procs starting with r_ is a route
• All routes calls forceHttpMethod that checks if the route is called using the correct HTTP method (useful in development and helps identify the routes by reading the code)
• In a if statement, try to put the error/fallback in the last
• Imports sequence is: std, pkg and local (current project)
• Each route file can have just one route
• in routes dir can have just routes because the filename is same as route name

• Hash the password
• Add user permission levels
• Add a route to delete user (for moderators?)
• Add route to get the logged user data
• Add login logging table
  • Add routes to get data (admin)
• Add last ip in User
• Add tests
• Support id for querying (Users)
• Add an error when no fields to edit was provided at /api/admin/editUser route
• Do the frontend (break it in smaller tasks)
• Fix email sending
• Add user activation
• Add user password reset
• Add honeypots or captcha
• Low priority: Add a temp block to multiple requests at same time to prevent DoS
• Block use of certain usernames and add filters. Like special chars
• Add a route to request new email validation Email resending
• Fix API to be REST (Resources: IBM, RestfulAPI)
  • Statelessness - Remove session verification at API, use some API key
• User activation as a code like Github
• Split route function to a function that can be called with custom data
• Fix file logging

MIT