Instalación de Doctrine

Hey @SoftwareDevs ,

There's a workaround on that thread you linked, probably you will need to go with that. I personally didn't have that issue, so I don't have a better workaround. It sounds like an issue in a specific version. You can track the status of the issue on that thread I think.

Cheers!

Hey @Ted

Could you corroborate you got that error from the code project of this tutorial? Also, does it happen on both directories (start, finish)? I'm asking because I just checked this course project and there are not any references to such environment variable

yes from the code project of this tutorial, it actually happens on both (start and finish) it also happens on the projects I tried to download form the next episodes in this tutorial, I followed along with Ryan since the first course and I started getting this error around the last episodes of the last course and I couldnt't solve it since. I'm following along with two computers to do the work twice and understand better but now I'm getting the error on both computers.

That's odd, I just gave it a try and could install the start directory of this project without any problems. This makes me think there's something going on in your local machine. Let's try to find where is that env var being used, run: git grep GITHUB_TOKEN
As a workaround, just define the env var in the .env file and try again

It's odd, i had the same issue today.

Interesting, thank you for reporting it @Stanislaw

I'll look deeper and fix the tutorial's code, in the meanwhile, you can go with my workaround

Cheers!

it is quite odd indeed, defining the variable in the .env file did the work. thank you

Hi there!

The env var is used in config/packages/framework.yaml when you download the course code - so that part isn't surprising. So then, where is it defined? In the previous episode, we added it to the "secrets vault" - and the dev (and prod) secrets vault IS included in the download - e.g. it's config/secrets/dev/dev.GITHUB_TOKEN.28bd2f.php. You should be able to see the secret by running:

php bin/console secrets:list --reveal

Anything in your secrets vault becomes an environment variable. So, this part is the mystery I think: why the GITHUB_TOKEN seems to be missing? Do you see it in the list when you run the above command (it should actually be the only env var returned in the list)? I have a feeling that your system may be missing the "sodium" PHP extension, which is normally part of core php, but I think some Linux distros may ship PHP without it (and then you can install it manually). Let me know if that's the case!

Cheers!

I had the same issue and installed the sodium extension by running
composer require paragonie/sodium_compat

It worked!

Hey Bartlomeij,

I don't think there're any other robust solutions. You can try to ignore platform requirements with --ignore-platform-reqs flag, but I'd not recommend it because it may cause issues in your code as it will use the new PHP syntax that will just not work on your PHP version.

So, you need either downgrade your PHP version or upgrade those required packages to a newer (most probably major) version. You can leverage https://packagist.org/ to see what version of the package requires what PHP version.

I hope this helps!

Cheers!

Howdy Benoit -

When I install it inside the directory it works better than outside.

This made me chuckle :) But to answer your question, yes - run composer install inside the start directory.

From this point on, you'll be doing everything from within the start directory. The finish directory is how your code should look at the end of the tutorial - assuming you're coding along with Ryan throughout the course.

Enjoy!

Yes, I think it would make me chuckle as well if I would read something like that :)

Could you take into consideration the way it is presented in the ReadMe file ?

Step 1 : (in whatever directory you are you should check that composer is installed properly)
So I would say that you should already mention that you are in the directory of your project at this stage.
In the Readme you are saying that you should only move to the directory later : "once on your system.
Then, to start the web server, open a terminal, move into theproject, and run ...":

Make sure you have Composer installed
and then run:

composer install

You may alternatively need to run php composer.phar install, depending
on how you installed Composer.

Start the Symfony web server

You can use Nginx or Apache, but Symfony's local web server
works even better.

To install the Symfony local web server, follow
"Downloading the Symfony client" instructions found
here: https://symfony.com/download - you only need to do this
once on your system.

Then, to start the web server, open a terminal, move into the
project, and run:

symfony serve

The problem is also that when I run git status I have a lot of files that are displayed and that should not be, right ?

Sorry for the slow reply,

Once you've extracted and moved into the start directory, you should be able to git init to initialize that directory as a git repository. git add . then git commit -m "starting the tutorial" to add and commit everything in start to the repo. Now when you run composer install, you will see a few files change - like composer.lock and possibly see a couple files added/changed due to Symfony's Flex recipe system. Those changes are ok to commit after running composer. Thanks to .gitignore you shouldn't see anything in git status related to say vendor/ and the like.

Does that sound about right for what you're seeing?

Hey Markchicobaby!

git status doesn't work because of course there is no git repo

Ha! Of course! I've been saying this type of thing for years without thinking about this fact! The hope is that you will initialize the git repository when you start via git init, but you're absolutely right that I don't say this. I'm going to be more careful with my language afterwards.

Cheers!

Hey Craig,

We're sorry to hear you're experiencing problems with our video player! I just double-check it, the video plays well for me around those 5:22, so it might be an internet connection issue on your laptop and so the video was not able to load from the server. Or, it might be a temporary outage of Vimeo video service - our video hosting provider. Please, try again today and let us know if the problem still persist. In this case, as a temporary workaround, I'd recommend you to download the video and watch it locally.

I hope this helps.

Cheers!

The video player still doesn't work for me in the website. The downloaded video works great. I don't have any trouble with any other videos on the site (I've watched dozens), so I assumed it was an issue with this video specifically.

Hey Craig,

Glad to hear you were able to watch the downloaded video in full locally. I'd recommend you to try a different browser, or probably a Chrome Incognito mode might help as well. But since you already watched it locally, you may just ignore :)

I still can't reproduce it for myself, so I think it should be good and most probably it's something local.

Cheers!