I'm developing a Tool using Symfony 2. Since my Version of Symfony is a bit old, I would like to update. My current installation is the one "with vandors" and I'm using it under Win7 with XAMPP.
I feel somehow stupid, but even after searching the internet for over an hour, I didn't figure out how to update correctly to Version .15
You would be a great help, if you could give me some dumb-secure instructions on this, because all I've done so far to install or patch software was running an exe-file.
Hopefully my english was good enough to point out what my problem is, but nethertheless I excuse myself for all mistakes.
Greetings GrimReaper1908
The update steps are always given in the release announcement (see Symfony 2.0.15 released):
If you already have a project based on the Symfony Standard Edition
2.0.x, you can easily upgrade to 2.0.15 by getting the new deps and deps.lock files. Then, run the vendors script (it also clears your cache):
./bin/vendors install
If you modified deps file to include additional vendors you'll have to manually merge it with the latest Symfony one.
Vendors script requires git client to work. You'll have to install it.
Since you're on windows: Symfony2 installing vendors in Windows
Related
I am trying to deploy symphony api project in hosting.
Until now, all the projects I have done have been pure php, uploading to hosting is simple and everything always works perfectly.
The situation with symfony is tragic and impossible for me, uploading the code just does not work.
I'm really very disappointed with the framework... deploying react, angular is so easy and here it's just ridiculously impossibly hard...
My question is not specific but I'm sure if there is a good answer it will be useful for thousands like me!
Can someone help me with this please? Any tutorial, video etc.
For 3 days I have been searching for information on Google and YouTube from morning to night all day like crazy.
I would appreciate it if someone could just send me a link to a blog tutorial or a video that works without third party applications. I am really tired...
Symfony is alive and well, just had a major developer conference in Paris days ago. Symfony has a new minor release every 6 months, a new version 6.2 will be released in the coming days.
Just make sure to follow the information for deployment linked above as well as the setup requirements: https://symfony.com/doc/current/setup.html#symfony-tech-requirements. Perhaps you are trying to run Symfony 6.1 with PHP lower than 8.1?
As to other backend frameworks like Laravel (which is based in part on Symfony): Almost everything in PHP land nowadays is using Composer for easy installation. Any hosting environment that provides SSH access should allow you to setup/use Composer.
A common pipeline to roll out projects can be IDE > GitHub > server. You can however use SFTP as well, just make sure that the program you are using follows the .gitignore file and doesn't try to upload everything. Afterwards run Composer and Yarn/NPM to install everything that your project needs.
the whole problem was in the version of composer, which is 1.0.0 in the hosting, which creates hundreds of errors and it is simply impossible to install the project written on the latest version.
All I had to do was manually install the latest version of composer on the hosting.
Then I install the project using the composer phar file
php ~/composer.phar install
instead of the default one which from the hosting is the oldest version 1.0.0 and bring impossible to fix problems.
If anyone has a similar problem just check the composer version in the hosting.
I've been using 1.1 on Win 10. When 1.2 came out, I tried upgrading but it actually falled back to 0.3. According to sashko a reinstall was necessary, which solved the problem for some. However, nothing happened when I uninstalled and rerun the installer. No files were actually modified. Deleting the %localappdata%/.meteor folder didn't help either. As the installer would no longer put anything there.
The farthest I could get is to get a dev build with a git clone, but I'd like to use a release version either 1.1 or 1.2. Otherwise I'm not able to update my project with a checkout meteor build.
Wrote a bunch of comments on other threads but none of the suggestions helped thus far, so I thought this deserves a new separate thread.
The solution was to clean the registry of meteor entries.
Credit goes to avalanche1 at: https://forums.meteor.com/t/windows-install-uninstall-hell/2375/7
Can someone explain me how should I install sts like some years back when I run some bash script and sts was installed ? With this new era when I just download sts and extract it to directory and run it I have a lot of problem. For example sometimes I can not open wsdl or xsd file in default editor and I need to use just text editor and so on. Here are error log of my sts:
http://pastebin.com/ePk7LnL2
I am using sts 3.6.3 download from this source: sts3.6.3
It looks like you installed additional plugins and it this looks like this caused a dependency issue between installed bundles. This disables certain bundles under the hood and that might cause the issues you describe.
I would recommend to download the latest STS 3.6.4 version and start with a test installation from scratch. Use that vanilla STS install to see what is working out-of-the-box and what not. If there is something not working, please file a bug at https://issuetracker.springsource.com/browse/STS. If everything works as expected, install add-ons step-by-step to figure out which install breaks something else.
That way we can find out what is going wrong and how to fix that specific problem then.
Hope this helps!
I have suddenly started getting the following message - all seems to work but i don't know why im getting it / what it really means for my app.
The only thing i can think of is that some smart-package im using is looking for an older version of meteor, and mrt is clever enough to not use a meteor version that will break it?
Stand back while Meteorite does its thing
Done installing smart packages
Ok, everything's ready. Here comes Meteor!
=> Running Meteor from a checkout -- overrides project version (0.6.2)
The thing is i'm pretty sure i want to be running on 0.6.2 not overriding it to some other version.
So what does this mean really? - and what do i need to do to not get it.
Thanks
I'm not too sure why it uses that odd terminology. Version 0.6.0 introduced project versions, so each project could run its own version of meteor similar to how meteorite does with smart.json
What Running Meteor from a checkout -- overrides project version (0.6.2) means is this version is overridden by the version in your smart.json. Typically the latest version on the master branch on github (which is checked out hence the wording). So at this moment if you ran mrt it would use 0.6.2.1
I'm sure over time meteorite will eventually be folded into meteor. 0.6.0 was just released a short while ago so some updates still need to be done to make them work better together.
I have a Plone installation at version 2.5.5. I need to upgrade it to 3.3.5. I'm not terribly familiar with Plone or Zope or Python.
This is in a windows 2008 R2 environment. I have the install files for both versions and I'm not worried about breaking anything because everything is backed up a dozen times.
The steps I've taken so far:
1) backed up the old files
2) tried installing 3.3.5 to the same directory...received several DLL entry point errors at the end of the process.
3) had to restart the computer
4) after restart the version 2.5.5 plone controller was still working but the 3.3.5 controller was not.
Did I do something wrong? The notes at www.plone.org/upgrade couldn't have been more unhelpful for my experience level.
Thanks for any advice!
http://plone.org/documentation/manual/upgrade-guide/
this is a good starting point, always.
Basically install Plone 3.3.X somewhere, install the same add-ons (and check compatibility, thus), copy the data.fs over and start plone 3. If it works, run the upgrade steps going in ZMI and following the noticies.
I think no Plone upgrade over major releases I have done went without complications.
My advice is to not upgrade in-place, but instead install the newer Plone version to another directory, create a new instance and copy the Data.fs file from the old site over to the new one. So you can at least compare your new to your old site, running side-by-side.
You then use the "migrate" product to update the database. Try using "dry-run" first. If you encounter errors during migration, try to disable the products that cause the error, and re-try.
That's -- roughly -- the advice from the Plone upgrade documents.