> For the complete documentation index, see [llms.txt](https://simian114.gitbook.io/blog/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://simian114.gitbook.io/blog/undefined/rubyonrails/undefined-3/css.md).

# css 파일을 수정했는데 적용이 안된다?

{% hint style="info" %}
[**rails assets-pipeline**](https://guides.rubyonrails.org/asset_pipeline.html)
{% endhint %}

현재 css 파일은 `assets` 폴더에서 관리가 된다. 이 폴더에서 관리가 된다는 건 `webpack` 으로 컴파일하는게 아닌 `sprocket` 에서 관리한다는 것.

따라서 `css` 파일을 수정해도 페이지에 들어갈 때 **컴파일**하지 않는 경우가 부지기수다.

이럴 때는 아래 명령어로 `assets` 을 컴파일 시킨다.

`rails assets:precompile`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://simian114.gitbook.io/blog/undefined/rubyonrails/undefined-3/css.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.