Improve setup instructions #8545
Conversation
024db0e to
8b381a9
Compare
- Separate database setup from server startup and clarifies asset handling process - Copy `cssbundling-rails` instructions from the Upgrading guide as a recommended approach for managing Tailwind CSS assets - Suggest starting the server with `bin/dev` to handle both web and CSS building process Ref: #8538 [ci skip]
8b381a9 to
ae6eeba
Compare
| rails importmap:install | ||
|
|
||
| bundle add cssbundling-rails | ||
| rails css:install:tailwind |
There was a problem hiding this comment.
It's not necessary to install tailwind. One can run command rails css:install and it should work.
There was a problem hiding this comment.
I mean, gem 'tailwindcss-rails' may not be installed
|
|
||
| ```sh | ||
| bundle add importmap-rails | ||
| rails importmap:install |
There was a problem hiding this comment.
As far as I know from my upgrade experience - it's also not necessary.
There was a problem hiding this comment.
rails importmap:install is not necessary because it is being performed by rails g active_admin:install
|
|
||
| ```sh | ||
| bin/dev | ||
| ``` |
There was a problem hiding this comment.
I think for those who doesn't have Procfile.dev you should give another option:
yarn build:css
rails s
|
Hi, I'm starting a new rails 8 app with active admin, and the styles didn't load at all, after following the basic guide. After some searching I came across this, and followed the commands, but I get Should I just go back to rails 7 for now and accept rails 8 and active admin are incompatible (is this actually the case)? Thanks. |
They are compatible: If you have some sort of edge cases, or different instructions, please provide more information so we can improve the installation guide edit: guide updated and tested again, I confirm that Rails 8.0 and Active Admin 4 beta are compatible
|
|
I still have no css after hours of effort. If I run I've googled "Error: Cannot find module 'tailwindcss/plugin'" and tried every possible fix I can find with no success. |
|
Is it possible to use active admin without tailwind? |
|
Can you please provide the list of commands that you are executing? Also please include Ruby and Node versions
Can't tell, maybe there are infos here: #8223 |
|
I am on an old node and osx, maybe that has something to do with it? |
This may be an issue, but we are not aware of such issue. I remember that I couldn't update to v4 with Node 16, but I need to check why |
|
I'm successfully running the application with node |
|
That did get further, staring from a new app from scratch. Now I get this:
|
|
looks like assets are not being build Can you try |
I am with this same problem here. I ran using
|
|
Hi, These are the instructions to create an app from scratch
|
Hi @tagliala , I was talking about the broken layout:
I followed all the steps here https://github.com/activeadmin/activeadmin/blob/master/UPGRADING.md to upgrade from v3 to v4 but I think the css is not being applied. |
|
Hi, just want to point out that this is a reasonable alternative to cssbundler if the goals are these:
bundle add dartsass-rails
echo "Rails.application.config.dartsass.builds = {\n 'active_admin.scss' => 'active_admin.css'\n}" > config/initializers/dartsass.rb
echo "sass: bin/rails dartsass:watch" >> Procfile.dev
bin/devI wonder if this could go into the |
I'm having a similar problem with the upgrade to 4. I notice that the generated css file only has a handful of tailwind classes. Perhaps it's not seeing all the classnames in the code that it needs to prevent them from being stripped out of the build? Did you manage to fix it? |
Hello, maybe I did not get this question. It's normal for Tailwind to remove unused CSS classes during the build process. Could you clarify your question or specify what you're expecting by using the discussion at #8538, since this pull request isn't related to the topic? Maybe it is related to the fact that now the latest stable Tailwind version is v4? Please ensure that v3 is being used |
That was exactly the issue. I had to pin to v3:
I assume that because of the many ways tailwind can be present, it doesn't make sense to have this as a hard dependency of the |
Correct. We can suggest a way, but the suggested way may not work with host application or developer preferences Additionally, we are in the middle of a migration to v4 and there is a new interesting (experimental) feature in tailwindcss-rails for engines, so this can change |
cssbundling-railsinstructions from Upgrading guide as a recommended approach for managing Tailwind CSS assetsbin/devto handle both web and CSS building processes.Ref: #8538
[ci skip]