A space to discuss and keep up software development and manage your software career
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
An inclusive community for gaming enthusiasts
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
A community of golfers and golfing enthusiasts
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating
Add a .gitignore to storage/framework with the following content:
.gitignore
storage/framework
* !.gitignore
Those are compiled views and should never be committed in the first place, so you can safely remove them by then typing git rm -r --cached storage/framework/*.
git rm -r --cached storage/framework/*
Then commit.
okay Thanks RVxLab
my current .gitignore is like :
/node_modules /public/hot /public/storage /storage/*.key /vendor .env .env.testing .env.backup .phpunit.result.cache Homestead.json Homestead.yaml npm-debug.log yarn-error.log .idea/ /public/img/avatars /public/js /public/css
`
What should I add exactly ?
Please re-read my comment, as I explained exactly what you need to do to fix this.
In case you didn’t know, it’s completely fine to have multiple .gitignore files.
/storage/* /storage/!.gitignore
and then run git rm -r --cached storage/framework/*
Not wrong. But also not what I said.
In case Mostafa didn’t know, it’s entire possible and legal to have multiple .gitignore files.
Possible, but from my personal experience it is better to have a single .gitignore file to rule them all 🙂
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Add a
.gitignoretostorage/frameworkwith the following content:Those are compiled views and should never be committed in the first place, so you can safely remove them by then typing
git rm -r --cached storage/framework/*.Then commit.
okay Thanks RVxLab
my current .gitignore is like :
`
What should I add exactly ?
Please re-read my comment, as I explained exactly what you need to do to fix this.
In case you didn’t know, it’s completely fine to have multiple .gitignore files.
and then run
git rm -r --cached storage/framework/*Not wrong. But also not what I said.
In case Mostafa didn’t know, it’s entire possible and legal to have multiple .gitignore files.
Possible, but from my personal experience it is better to have a single
.gitignorefile to rule them all 🙂