-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Setup deployment for canary branch #3909
Comments
I'm not sure what we need to add in the canary branch, but let me start with upgrading nuxt-edge and trying to add oruga I think migrating the vue component to composition API, it's better directly to the oruga + tailwindcss seems a good match, isn't it? tailwind has a good extension https://tailwindcss.com/docs/editor-setup#intelli-sense-for-vs-code, and we can put our sass variable in the tailwind config. so our variable will appear on the IntelliSense |
I'm okay with that, it can remain invisible to end users.
🤔? |
The goal is to have something that help us to maintain the components (in neobrutalism style) without mess. |
since we want to refactor the components. do we want/need to implement monorepo/workspace stuff?
the downside:
after we use the monorepo/workspace structure, maybe we can implement https://turborepo.org/showcase also and put our logo there |
With Vik briefly chatted and his idea was to make it as components through packages iirc, otherwise I'm up to for new structure as now it's good time to change this |
Maybe the best steps for now:
|
yes, I think that is the downside if the package/component is in a separate repo. but we can discuss it in more detail once we land vue3 in the components so, here is a summary of todos:
is that correct? did I miss any step? |
Updated with |
it's no longer relevant? |
I think we working JIT in beta. |
I think we can have https://canary.kodadot.xyz which could be |
can we have a canary on cloudflare-pages? for |
aaa, I think issue is you won't visit deploy preview until I add you to the CF ? can you get deploy in incognito easily? #5416 |
aaa, seems can be deployed only once and doesn't support domains per aliases per branch, only aliases for one deployments which is not case we needand accidentally turn on zerotrust access policy and can't return it back ommmm and it probably requires some sophisticated settings for deploy preview access and maybe is possible at least fix one thing 😅 well in worst case, I'm happy to have.. CF deploy to have consistency towards production and development keep netlify bc what I recall it possible much easier, in worst case explore CF setup one more time |
Set Netlify branch deployment for
canary
branchOnce there is something in Canary branch, can proceed
Best if it would be straight working something with Vue3 components
The text was updated successfully, but these errors were encountered: