Adrimarie I posted the same issue for help at another support community and suggested that I chmod 777 for it to work. Obviously didn't work lol.
See my Rant below (it is not necessary for understanding / fixing your issue, nor is it criticizing you (the one asking for help) in any way)
So, if I do this rm -r foldername && composer create-project flarum/flarum foldername --stability=beta line, do I do it outside the wellspringdreams.club folder?
What this does is:
- Removes
foldername
recursively (means it will remove directories and files contained within foldername
&&
means it will only run the next command if the preceding command was successful.
composer create-project flarum/flarum foldername --stability=beta
creates the directory foldername
, then downloads the files for flarum inside that directory.
In your case, removing the wellspringdreams.club
folder and recreating it, then filling it with flarum files.
If that doesn't make sense or doesn't work, let us know.
Adrimarie I'm still new to SSH access shell and the terminal commands, and still getting used to it.
This is somewhat offtopic, but I'm going to recommend some documentation for learning bash (the ssh terminal commands) and other components of linux - feel free to examine them or not. ?
The Linux Documentation Project (Overview)
http://www.tldp.org/
Command line
https://flossmanuals.net/command-line/index/
Etc
Understanding how linux uses Ram - http://www.linuxatemyram.com/
Why linux doesn't need defragmentation - http://geekblog.oneandoneis2.org/index.php/2006/08/17/why_doesn_t_linux_need_defragmenting
Metaphorical comparsion of windows / linux http://linux.oneandoneis2.org/LNW.htm
Iptables firewall (excellent introduction to layers of networking!) - https://www.frozentux.net/documents/iptables-tutorial/
Open a terminal and read through
man man
- Learn how to search for information and navigate quickly through the page
man bash
- Learn about pipes, quoting, if tests / while and for loops (use search engines for what you don't understand)
man hier
- Linux filesystem
man ssh
-
man sshd
- Read this one and learn how to use keys and not passwords. Also relevant
Learn vi / vim and nano. Even if you don't want to use a command line editor, knowing how to use one could save you from a otherwise catastrophic incident.
man vi
- :q!
forces a quit from the program ?
man nano
vimtutor
(may need to install vim)
Rant:
I'm curious what their rationale was for suggesting chmod 777
. To be explicit - chmod 777 foldername
changes the permissions
for foldername
to read + write + execute for owner, group and world (all) users
It's useful for permissions errors because it allows you to say "it is not a permissions error" as the summary of that is "make it so everybody on this computer do whatever they want with this directory."
Notice the possible security issue? ?
Assuming that user had the same info I do, why suggest advice to resolve a Permissions Error when it's fairly clear it's a issue with the folder not being empty and not a permissions issue - it sounds like regurgitated advice. That is, blindly give advice they heard without really understanding what that advice does and what scenarios it applies too, hoping it fixes "things".
It's ok to not understand what you're being told, but to give advice without understanding what it does can easily make things go from bad to worse. For example, a common variation is chmod -R 777
which does the same but now it's recursive. Or for removing files to use -rf
which means, "whatever it takes to remove all these files / directories (-r
) - do it and don't ask me if there's a issue (-f
) (like removing /
, or many files, or files that are write protected, or that you don't have permission to remove these files and maybe that's something you should notice)
Ok rant over.