-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue upgrade from v2.0.6 to v2.1.0-pre #1556
Comments
|
Actually, does pre-release version different than "Production" version that's why the last command shows "Nothing to migrate"? |
There is a known issue in the auto-versioning of the script, so don't pay attention to that, really. If you have Admin > Custom Fields, and you pulled from master or the latest release, you should be fine. I'm not sure what you're asking about pre-release versus Production. A pre-release is one that's ready for testing, and is considered reasonably stable, but isn't considered a truly stable release yet. Stable release will not be marked as "pre-release". |
I don't have Admin > Custom Fields seems some luck coming as it runs migration script but error showing as below. Do i need to stop any service before calling "php artisan migrate"? Any idea? Thank you!! php artisan migrate
Do you really wish to run this command? y [Illuminate\Database\QueryException] [PDOException] migrate [--bench[="..."]] [--database[="..."]] [--force] [--path[="..."]] [--pac kage[="..."]] [--pretend] [--seed] |
tried but no luck this time I read another post (#1430) to rerun "# php composer.phar install --no-dev --prefer-source" and delete "2015_11_30_191504_remove_fk_company_id.php" at app/database/migrations then redo all over again. However, i still don't see "custom fields" under "Admin" menu. MariaDB [(none)]> use snipeit; Database changed MariaDB [snipeit]> exit -# php composer.phar install --no-dev --prefer-source Loading composer repositories with package information Generating autoload files -************************************** Do you really wish to run this command? y |
Can you tell me what's in your migrations table? |
MariaDB [snipeit]> select * from migrations; |
any idea? |
Finally i got some luck here. i don't know what i did wrong but i uninstall mysql and reinstall everything again. It works perfectly and now it shows v2.1.0-pre-g4aa3768 with custom fields. Thank you! |
Hi,
My current version is v2.0.6-14-g74ed75d. I tried to follow the instruction guide below to upgrade to v2.1.0-pre, however, seems not working. Any idea? Below are the screens of my upgrade process. Thank you!
[root@XXXXXXXXXXXX snipeit]# php composer.phar install
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
Downloading: 100%
sebastian/global-state suggests installing ext-uopz ()
phpunit/phpunit-mock-objects suggests installing ext-soap ()
phpunit/php-code-coverage suggests installing ext-xdebug (>=2.2.1)
phpdocumentor/reflection-docblock suggests installing dflydev/markdown (~1.0)
phpunit/phpunit suggests installing phpunit/php-invoker (~1.1)
codeception/codeception suggests installing codeception/phpbuiltinserver (Extension to start and stop PHP built-in web server for your tests)
codeception/codeception suggests installing codeception/specify (BDD-style code blocks)
codeception/codeception suggests installing codeception/verify (BDD-style assertions)
Generating autoload files
[root@XXXXXXXXXXXX snipeit]# php composer.phar dump-autoload
Generating autoload files
[root@XXXXXXXXXXXX snipeit]# php artisan migrate
Do you really wish to run this command? y
Nothing to migrate.
[root@XXXXXXXXXXXX snipeit]# php artisan migrate
Do you really wish to run this command? yes
Nothing to migrate.
The text was updated successfully, but these errors were encountered: