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

Recommend static directory structure for easy deployment #5

Open
nikochiko opened this issue Sep 13, 2022 · 0 comments
Open

Recommend static directory structure for easy deployment #5

nikochiko opened this issue Sep 13, 2022 · 0 comments

Comments

@nikochiko
Copy link
Contributor

nikochiko commented Sep 13, 2022

Currently, user has to make too many changes to the configuration we provide (edit inside the files) and rename directories from X to Y.
The recommended installation installs in /home/$user directory.

The recommended installation should be in a directory like /etc/ or /var/ which won't change across installations.

Maybe, a good directory structure could be like this:

/etc/hamr/
|__ apps/
|__ |__ app1/wsgi.py
|__ |__ app2/wsgi.py
|__ code/
|__ |__ LICENSE
|__ |__ hamr/
|__ |__ |__ __init__.py
|__ |__ |__ api.py
|__ config.yml
|__ hamr.cgi
|__ hamr.conf  # apache

This looks clean and puts the mess of code into one directory. But this also adds instructions for users to move out the config.yml and hamr.cgi from the root of repository.

Maybe, we can structure the repo so that the user just needs to clone the repo into /etc/, symlink apache configuration, enable mods and the site, and then it just works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant