Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

chore: bump loco to 0.14.0 #202

Merged
merged 3 commits into from
Jan 14, 2025
Merged

chore: bump loco to 0.14.0 #202

merged 3 commits into from
Jan 14, 2025

Conversation

jonaro00
Copy link
Member

Description of change

updates loco hello-world template to what you get with latest main on loco (after loco-rs/loco#1169 merged), loco new + cargo loco generate deployment --kind shuttle

How has this been tested? (if applicable)

local run and deploying works

@jonaro00
Copy link
Member Author

cc @kaplanelad @jondot

@kaplanelad
Copy link
Contributor

Great!

We also have additional templates available:

  • API server with a database
  • Server-side rendering using HTMX/HTML
  • Client-side rendering

Let me know if you're interested, and I can open a PR to add these templates

@jonaro00
Copy link
Member Author

Since loco new + generate deployment is more sophisticated than shuttle init, I think we can keep this repo to the minimal example to reduce maintenance burden, and encourage loco new.

@jonaro00 jonaro00 merged commit 0a3a9bb into shuttle-hq:main Jan 14, 2025
3 checks passed
@jonaro00 jonaro00 deleted the loco-14 branch January 14, 2025 12:34
@kaplanelad
Copy link
Contributor

@jonaro00
When I run shuttle init and select a template from one of the supported frameworks, the current suggestion for Loco is an API template without database integration.

I believe adding another template that includes database integration—seamlessly configured to work with Shuttle—would provide significant value to customers.

@jonaro00
Copy link
Member Author

True. Created #203

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants