There are a collection of application templates, scripts, and automatizations I use for everyday work. All included code is written with the following principles:
- Code is testable
- Code is written to be supported without a hassle
- Code is written, following best practices from developers and product communities
Feel free to submit any feature or pull request if you think that it may be useful for the community.
rails new APP_NAME --no-skip-hotwire -T -c tailwind -j esbuild -d postgresql -m https://raw.githubusercontent.com/alec-c4/ks-rails-tailwind/master/template.rbrails new APP_NAME --no-skip-hotwire -T -c bootstrap -j esbuild -d postgresql -m https://raw.githubusercontent.com/alec-c4/ks-rails-bootstrap/master/template.rbrails new APP_NAME --api -T -d postgresql -m https://raw.githubusercontent.com/alec-c4/ks-rails-api/master/template.rbrails new APP_NAME -T -d postgresql -m https://raw.githubusercontent.com/alec-c4/ks-rails-basic/master/template.rb
npx degit alec-c4/ks-sveltekit-starter APP_NAME
npx degit alec-c4/ks-nextjs-starter APP_NAME
- Monolith ruby on rails application with tailwindcss frontend
- Monolith ruby on rails application with bootstrap frontend
- Rails API application
- Rails basic/plain application
- SvelteKit basic template
- Next.js basic template
- Add monolith ruby on rails template with inertia.js frontend
- Add Nest.js template
- Add ansible templates for rails and js applications
- Add terraform templates for DigitalOcean, Linode and AWS
not found
For bug fixes, documentation changes, and features:
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create a new Pull Request
For larger new features: Do everything as above, but first also make contact with the project maintainers to be sure your change fits with the project direction and you won't be wasting effort going in the wrong direction.