-
Notifications
You must be signed in to change notification settings - Fork 623
Add tuxseo.yml #1646
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
Add tuxseo.yml #1646
Conversation
|
This is a remake of #1633 I renamed the project and updated deployment options/instructions as per comments in that previous PR. Thought it made sense to create a new PR. Apologies if my assumptions were wrong and should have kept it in the previous one. |
|
@kokomo123 thanks for the review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, as appropriate changes have been made pending further thoughts from collaborators. Thank you 👍🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Automation is different than automating content creation
Co-authored-by: Kieran <32241933+Ki-er@users.noreply.github.com>
|
@Ki-er make sense about automation. updated |
Co-authored-by: nodiscc <nodiscc@gmail.com>
|
@nodiscc , if you have time do you mind reviewing? Thanks a ton in advance |
|
Apologies for the stupid question, but what happens now after the reviews are done? |
|
Thanks for taking the time to suggest an addition to awesome-selfhosted!
To ensure your Pull Request is dealt with swiftly, please check the following (check the boxes
[x]):Demolinks should only be used for interactive demos, i.e. not video demonstrations. If login credentials are required to access the demo, please link to the credentials directly.my-awesome-software.yml.platformare the main server-side requirements for the software. Don't include frameworks or specific dialects.