what is the best way to use an exist laravel project to create a new project.I copied my project floder and I renamed it but it does not work
Please, somebody help me!
You will still need to install the dependencies through composer as well as any node dependencies you have.
Run composer update on the new project.
Also make sure your file permissions are correct on the new project.
In my opinion the best way to do this is Version Control System.
Step 1: Create Repo of your existing project
Step 2: Fork your Repo, this will allow to choose another project name and so on
You will be able to use your first Repo as template any time when you will need without copy/paste of files on your local
Related
Im very new to laravel and ive a project on a server that uses laravel.
How can i download this project and run laravel to it ? I managed to run laravel but it creates a whole new folder etc.
when i tried coppying the project folder to the laravel-created folder i got an error.
Download source code except vendor casus it's extra. Install php and composer. Then use a terminal(cmd in windows) and go to your project and run composer install. Wait till downloading packages complete. For running project type php artisan serve and your project is up. If your project had migrations and I think it has actually, run php artisan migrate before running serve command. Also check .env file in the root of project and change database credentials with your own. Depending on what dbms that project uses, you should install that DBMS too. Good luck
Taking reference to your comment:
i have the source code of a project that runs on laravel. Basicaly i am asking how can i run this source code localy on my pc
Good, that you have a project that runs on Laravel. You should probably consider to move your project to a central place, maybe Github, and from there create a proper workflow for development and further deployment to your (testing, production, ...) systems.
Even if you develop alone it would be a good practice to use git and Github - no, it is not the same
To come back to your original question:
How can i download this project and run laravel to it ? I managed to run laravel but it creates a whole new folder etc.
You don't need to install a new Laravel into an existing Laravel project. Just take the existing one.
I have scoured the web for hours but I can not seem to wrap my head around this. I am developing a Laravel project where I am using the dependency UniSharp/laravel-settings. However, I have noticed that after upgrading my Laravel version to 6.0, the package breaks. I have figured out what I need to do to make the package work with Laravel 6.0 and now I wish to make the required changes and then use the modified package.
So far, I have cloned the original repository into my own (i.e realnsleo/laravel-settings) and I have cloned it onto my development machine. The trouble is, I don't know how to test whether my changes work. Do I need to setup a fresh Laravel installation to test the package? I noticed the package has it's own composer.json file, should I install those dependencies separate from the installed Laravel project? I am highly confused.
Can someone assist me with a step by step on what I need to do to achieve this? I will highly appreciate it. Thank you.
I'm developing with Laravel a suite of applications which are very different from each other, but must have the same base (graphics-functions-components-login-ecc.).
I just finished the base project, which I simply called 'template', and which is under git-versioning.
Now I have to develop the real applications, which will be extensions of 'template', but I want to keep pulling the base from 'template' and create some sort of 'git extension' for each application.
I would like to do this to keep the laravel tree structure of the project (so not use external folders) while avoiding to update each single application when I modify the 'template'.
I thought about link the same project folder to two different repositories (template+extension), using 'gitignore' to manage which file links to which repository, but I think it could be troublesome in case of new file added or so.
Maybe git has already an existing way to solve this, but I'm quite new and not expert to this, so I hope you'll guide me to the light.
You can use git Submodules. Submodules are Git repositories nested inside a parent Git repository at a specific path in the parent repository’s working directory. For detail visit https://git-scm.com/docs/git-submodule.
I've created a custom project template the needs to add a few submodules upon creation of the new project. I have the git submodule add ... command added to a .sh file. So is it possible to automatically run the script after creating the project without having to add it to the Build Phases? Maybe through the TemplateInfo.plist? If you know any alternatives or better routes to take, please let me know.
Thanks
Considering a submodule is just a reference to a fixed SHA1, you could simply add them directly to your template project.
That way, any new project would already benefit from said submodules.
I currently have an Xcode project which has a remote in the organizer for a Bithucket repository. I want to start the project over with a fresh template. However I do not want to lose all my previous commits I just want a brand new project in Xcode but to Bitbucket it should just be like another commit. How do I go about in doing this? I would like instructions on what I do in Xcode and what I do in Bitbucket. Thanks in advance!
I've never used the built in git client in XCode, but one idea would be to create the new project, migrate over the .git folder and .gitignore (if there is one) together with the source files and resources you may need.
I'm bit curious to why you'd want to create a new project.
I'd also recommend using the terminal version of git, but that's just an aside.
It sounds like you might actually want a new project hosted on BitBucket. You have unlimited private repositories; use them.
If for some reason you want to use an anti-pattern, you could just create a separate branch for each of your products. It is much better to just create another repository for new projects though. Otherwise, it is not clear what you are tracking in the repo.