Skip to content
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

Jump to bottom

Homestead v11.0.0 - General Upgrade Notes #1422

Closed
svpernova09 opened this issue May 16, 2020 · 12 comments
Closed

Homestead v11.0.0 - General Upgrade Notes #1422

svpernova09 opened this issue May 16, 2020 · 12 comments
Projects
Focal Update - Major Version Bump

Comments

@svpernova09
Copy link
Collaborator

svpernova09 commented May 16, 2020 •
edited

New Features 🆕

Enable or Disable Services

Homestead starts several services by default however if your configuration overrides one of these defaults you can specify which services you would like to enable or disable during provisioning. For example if you only needed PostgreSQL 12 your services: configuration in Homestead.yaml might look like:

services:
    - enabled:
        - "postgresql@12-main"
    - disabled:
        - "mysql"

This configuration would ensure postgresql@12-main service would be enabled and mysql would be disabled from starting at boot. The specified services will also be started or stopped based on their location in enabled and disabled sections.

New Default Versions

  • Ubuntu 20.04
  • MySQL 8 (mysql8 feature script removed)
  • Node 14

General Notes

Wildcard SSL

Homestead configures a self-signed SSL certificate for each site defined in the sites: section of your Homestead.yaml file. If you would like to generate a wildcard SSL certificate for a site you may add a wildcard option to that site's configuration. By default the site will use the wild card certificate instead of the specific domain certificate.

- map: foo.domain.test
  to: /home/vagrant/domain
  wildcard: "yes"

If the use_wildcard option is set to no, the wildcard certificate will be generated but will not be used:

- map: foo.domain.test
  to: /home/vagrant/domain
  wildcard: "yes"
  use_wildcard: "no"
@svpernova09 svpernova09 created this issue from a note in Focal Update - Major Version Bump (In progress) May 16, 2020
@svpernova09 svpernova09 changed the title General Upgrade Notes Homestead v11.0.0 - General Upgrade Notes Jun 14, 2020
@svpernova09
Copy link
Collaborator Author

Beta: https://github.com/laravel/homestead/releases/tag/v11.0.0-beta

@yabasha
Copy link

yabasha commented Jun 15, 2020

after upgrading to this version, I receive the following message after entering vagrant up

code-server: Job for nginx.service failed because the control process exited with error code.
    code-server: See "systemctl status nginx.service" and "journalctl -xe" for details.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

systemctl status nginx.service output:

nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2020-06-15 07:57:28 UTC; 11min ago
       Docs: man:nginx(8)
    Process: 954 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)

Jun 15 07:57:27 homestead systemd[1]: Starting A high performance web server and a reverse proxy server...
Jun 15 07:57:28 homestead nginx[954]: nginx: [emerg] cannot load certificate "/etc/ssl/certs/*.code-snippet.test.crt": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/ssl/certs/*.code>Jun 15 07:57:28 homestead nginx[954]: nginx: configuration file /etc/nginx/nginx.conf test failed
Jun 15 07:57:28 homestead systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Jun 15 07:57:28 homestead systemd[1]: nginx.service: Failed with result 'exit-code'.
Jun 15 07:57:28 homestead systemd[1]: Failed to start A high performance web server and a reverse proxy server.

my Homestead.yaml file:

---
ip: "192.168.20.20"
memory: 4096
cpus: 4
provider: virtualbox
name: code-server

authorize: ~/.ssh/id_rsa.pub

keys:
    - ~/.ssh/id_rsa

folders:
    - map: code
      to: /home/vagrant/code
      options:
          fsnotify: true
          exclude:
              - node_modules
              - vendor

backup: false

variables:
    - key: APP_ENV
      value: local

sites:
    - map: project.test
      to: /home/vagrant/code/project/public
      wildcard: "yes"

databases:
    - project_db

features:
    - mariadb: false
    - ohmyzsh: true
    - webdriver: false

ports:
    - send: 3000
      to: 3000
    - send: 50000
      to: 5000
    - send: 7777
      to: 777
      protocol: udp

Also, I tried to include

services:
    - enabled:
        - "mysql"
    - disabled:
        - "postgresql@12-main"
        - "nodejs"

but the same error message appeared.

Please advice,

@svpernova09
Copy link
Collaborator Author

svpernova09 commented Jun 15, 2020 via email

@eminos
Copy link

eminos commented Jun 20, 2020 •
edited

How do I try v11 using the "per project installation"?
I've tried changing the composer.json to "laravel/homestead": "^11@beta", and then composer update. Which seems to work fine. But how do I update the Vagrantfile in the project root?
Running vendor\laravel\homestead\init.bat results in:

The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
Homestead initialized!

Running vagrant box update results in my-project: Box 'laravel/homestead' not installed, can't check for updates.

vagrant up fetches the v9.5 box. Adding box 'laravel/homestead' (v9.5.1) for provider: vmware_desktop

[EDIT]

Seems the v10 box is not available for vmware.
https://app.vagrantup.com/laravel/boxes/homestead

@svpernova09
Copy link
Collaborator Author

svpernova09 commented Jun 21, 2020 via email •
edited

@svpernova09
Copy link
Collaborator Author

MongoDB support coming soon: https://jira.mongodb.org/browse/SERVER-44070

@svpernova09
Copy link
Collaborator Author

Releasing new base box https://app.vagrantup.com/laravel/boxes/homestead/versions/10.0.0-beta.1

@svpernova09
Copy link
Collaborator Author

How do I try v11 using the "per project installation"?
I've tried changing the composer.json to "laravel/homestead": "^11@beta", and then composer update. Which seems to work fine. But how do I update the Vagrantfile in the project root?
Running vendor\laravel\homestead\init.bat results in:

The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
Homestead initialized!

Running vagrant box update results in my-project: Box 'laravel/homestead' not installed, can't check for updates.

vagrant up fetches the v9.5 box. Adding box 'laravel/homestead' (v9.5.1) for provider: vmware_desktop

[EDIT]

Seems the v10 box is not available for vmware.
https://app.vagrantup.com/laravel/boxes/homestead

Sorry for the delay, Yes, I typically only build Virtualbox for pre-release builds due to the time investment in building & releasing a base box. Example: Tonight I'm releasing a new beta base box and it's taken me 2.5 hours instead of 1.5 hours due to random APT / network timeouts. Unfortunately, it's just a big time investment :/

@litan1106
Copy link
Contributor

Give this a spin: composer require laravel/homestead:dev-focal-major-version
…
On Sat, Jun 20, 2020 at 12:07 PM Emin @.> wrote: How do I try v11 using the "per project installation"? I've tried changing the composer.json to "laravel/homestead": @.", and then composer update. Which seems to work fine. But how do I update the Vagrantfile in the project root? Running vendor\laravel\homestead\init.bat results in: The system cannot find the file specified. The system cannot find the file specified. The system cannot find the file specified. Homestead initialized! Running vagrant box update results in my-project: Box 'laravel/homestead' not installed, can't check for updates. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1422 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHMFQWVAXFK6X6HLCGSHXLRXTUD5ANCNFSM4NDASE5Q .
-- - Joe Ferguson JoeFerguson.me osmihelp.org

Nice. MongoDB is a must for me.

@svpernova09
Copy link
Collaborator Author

@eminos https://twitter.com/HomesteadDev/status/1280273116174958592 You should be able to beta test 20.04 now.

@svpernova09
Copy link
Collaborator Author

Release incoming

Focal Update - Major Version Bump automation moved this from In progress to Done Jul 21, 2020
@litan1106
Copy link
Contributor

General Notes

Mongo support 20.04(focal) in v4.2 now.
https://docs.mongodb.com/manual/tutorial/install-mongodb-on-ubuntu/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
No open projects
Focal Update - Major Version Bump
  
Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@yabasha @svpernova09 @litan1106 @eminos