Skip to content
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

feat: support "minimalist" Bridgetown projects #941

Open
jaredcwhite opened this issue Nov 20, 2024 · 2 comments
Open

feat: support "minimalist" Bridgetown projects #941

jaredcwhite opened this issue Nov 20, 2024 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@jaredcwhite
Copy link
Member

jaredcwhite commented Nov 20, 2024

I thought there was an issue like this floating around, but I couldn't find it exactly so here's a new shiny one.

From time to time, I noodle around with experimental project folders which have the fewest amount of config files possible. The idea is that a "minimalist" install of Bridgetown could build/service a folder with virtually no config files…ideally, only Gemfile! (so config.ru optional, as well as a Node-less environment)

@jaredcwhite
Copy link
Member Author

Hmm, is there a bug with start --source=foldername if using something other than the default src?

@jaredcwhite
Copy link
Member Author

Yes there was! I think we may have a remaining timing issue with when certain paths get set across defaults, CLI options, and the initializers file, but we should file those separately if so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant