No description
Find a file
2021-10-22 18:33:04 +00:00
.gitlab feat: Add cypress for integration testing 2021-08-12 19:07:19 +00:00
apps chore(release): 3.0.4 [skip ci] 2021-10-22 18:33:04 +00:00
config fix: Correct path for social media preview images 2021-10-22 10:00:32 -05:00
infrastructure chore(release): 3.0.4 [skip ci] 2021-10-22 18:33:04 +00:00
infrastructure_templates fix: Force POOL_SIZE value to string 2021-10-22 13:19:54 -05:00
priv fix: Provide empty priv directory for mnesia startup 2021-06-01 12:10:57 -05:00
script chore: Try to unstick hex DNS 2021-09-26 22:21:52 -05:00
.dialyzer_ignore.exs chore: Address a variety of warnings 2021-08-04 16:32:13 -05:00
.dockerignore fix: Create priv folder for mnesia in docker image 2021-09-26 16:52:26 -05:00
.formatter.exs feat: Commit initially 2020-07-02 16:08:53 -05:00
.gitignore feat: Add object_storage engine and social media preview image generation 2021-10-19 19:28:25 +00:00
.gitlab-ci.yml fix: Upgrade dependabot-gitlab image version for CI 2021-09-15 17:23:53 -05:00
.tool-versions chore(deps-dev): bump semantic-release from 17.4.7 to 18.0.0 2021-09-23 23:08:45 +00:00
Brewfile fix: Only install asdf from brew if it does not exist on system 2021-08-16 16:26:58 -05:00
Dockerfile fix: Add object_storage/mix.exs to Docker image 2021-10-22 10:00:32 -05:00
lefthook.yml feat: Prettier and stylelint in CI 2021-07-20 17:42:40 -05:00
LICENSE feat: Add documentation 2021-03-19 10:29:49 -05:00
mix.exs chore(release): 3.0.4 [skip ci] 2021-10-22 18:33:04 +00:00
mix.lock fix: Adjust social media preview image dimensions 2021-10-22 10:44:58 -05:00
package-lock.json chore(deps-dev): bump @semantic-release/npm from 7.1.3 to 8.0.0 2021-09-25 21:56:59 +00:00
package.json chore(release): 3.0.4 [skip ci] 2021-10-22 18:33:04 +00:00
README.md fix: Share sessions between multiple pods 2021-05-28 12:38:37 -05:00

Overview

Legendary is a boilerplate for developing PETAL-stack Phoenix/Elixir applications without reinventing the wheel. Out-of-the-box, we include many features that are commonly needed in web applications:

  • Features
    • Authentication & Authorization
    • Admin interface & dashboard
    • Lightweight content management / blogging
    • Background & scheduled jobs with Oban
  • Frontend Frameworks
    • Tailwind CSS
    • Alpine JS
    • Fluid HTML email templates
  • Full CI / DevOps scripts included

We got tired of setting these things up from scratch on every Phoenix application. So, we built a boilerplate that lets you start with the unique & interesting thing that only your application does. We have a roadmap for future feature development because we still think there are a lot more things we can do to make Phoenix development better.

Up and Running

In order to start the server, run script/server. Any dependencies required will be installed automatically using brew, asdf, and hex.

Now you can visit localhost:4000 from your browser.

Application Development

Your main app lives in apps/app/ and that is where you will do most of your development there. This is a normal Phoenix application and you can develop it as such. Any resources which apply to developing Phoenix applications will apply inside of the app. See the Phoenix Guides for a good starting resource in Phoenix development.

You should not generally need to change code in the other applications which are part of the framework-- admin, content, core. We encourage you to avoid changing those as much as possible, because doing so will make it more difficult to upgrade Legendary to newer versions. However, they are available to you if you find that there are no other ways to accomplish the changes you want to accomplish. If you find yourself adding functionality to admin, content, or core that you feel would be beneficial to all Legendary apps, consider making a code contribution back to the framework!

CI Configuration

Legendary comes with gitlab CI settings which should work for you with minimal setup.

The CI script will automatically tag successful builds. To do this, you will need to configure a CI variable named GITLAB_TOKEN. This token should be a personal access token with read_repository, write_repository permissions.

Support

Want to support development? Chip in on buymeacoffee:

Buy Me A Coffee