Gitea actions seems to be compatible with GitHub Actions and can use published actions from GitHub.
Integration
Probably don't need this but you can add in checks for code linting via Pint and running tests via PHPunit.
You can spawn a MySQL or MariaDB container to run your database related stuff so it gets proper testing.
We've got some examples of this for the NOC and Bug Reporter.
Deployment
I would recommend utilizing Deployer for performing the deployments, this'll give a lot of benefits such as deploying from any machine with SSH access and allowing you to rollback to previous releases easily.
I would recommend and triggering automated deployments when a new release has been created in Gitea.
We've got some examples of this for the NOC and Bug Reporter.
Progress
Continuous Integration
Continuous Deployment
Gitea actions seems to be compatible with GitHub Actions and can use published actions from GitHub.
### Integration
Probably don't need this but you can add in checks for code linting via Pint and running tests via PHPunit.
You can spawn a MySQL or MariaDB container to run your database related stuff so it gets proper testing.
We've got some examples of this for the NOC and Bug Reporter.
### Deployment
I would recommend utilizing [Deployer](https://deployer.org/) for performing the deployments, this'll give a lot of benefits such as deploying from any machine with SSH access and allowing you to rollback to previous releases easily.
I would recommend and triggering automated deployments when a new release has been created in Gitea.
We've got some examples of this for the NOC and Bug Reporter.
### Progress
- [ ] Continuous Integration
- [x] Continuous Deployment
The release one is working 100% I cannot remember the state of the others
I also have some examples of gitea CI/CD working here
https://git.lovelynet.net/benjamyn/CyberChef/src/branch/master/.github/workflows
The release one is working 100% I cannot remember the state of the others
llama
added this to the PriceyBotPanel project 2023-10-11 21:35:42 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Gitea actions seems to be compatible with GitHub Actions and can use published actions from GitHub.
Integration
Probably don't need this but you can add in checks for code linting via Pint and running tests via PHPunit.
You can spawn a MySQL or MariaDB container to run your database related stuff so it gets proper testing.
We've got some examples of this for the NOC and Bug Reporter.
Deployment
I would recommend utilizing Deployer for performing the deployments, this'll give a lot of benefits such as deploying from any machine with SSH access and allowing you to rollback to previous releases easily.
I would recommend and triggering automated deployments when a new release has been created in Gitea.
We've got some examples of this for the NOC and Bug Reporter.
Progress
I also have some examples of gitea CI/CD working here
https://git.lovelynet.net/benjamyn/CyberChef/src/branch/master/.github/workflows
The release one is working 100% I cannot remember the state of the others
Implemented in PR #26