We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think the most sensible way to package Otto at the moment would be to create a meta package called otto and then a package for:
otto
osp
Ideally these could all be installed on one machine or installed on different machines.
The text was updated successfully, but these errors were encountered:
I think /etc/otto should be conventionally used for configuration, under that should be an otto.yml and projects.d
/etc/otto
otto.yml
projects.d
Sorry, something went wrong.
No branches or pull requests
I think the most sensible way to package Otto at the moment would be to create a meta package called
otto
and then a package for:osp
and other development utilities for the future)Ideally these could all be installed on one machine or installed on different machines.
The text was updated successfully, but these errors were encountered: