SBT 1.0+ Resolvers no longer using Credentials? - sbt

this is related to the last question I posted on the subject:
SBT Publish to Visual Studio Team Services (Web) Packages Plugin Repo
At the time I wrote that I was running SBT 0.13.16, and was able to make everything work.
My team has attempted since then to upgrade to SBT 1.0.x, and while for a while it seemed to work, it turns out that was only thanks to the cached versions of our libraries in ivy.
Attempting a clean setup using the same technique that worked in SBT 0.13.16 results in no attempt to send authentication information to the servers (and thus, no library download and frustrated devs); verified with Fiddler.
PUBLISHING does work and seems to make proper use of the credentials, but DEPENDENCY RESOLUTION does not, any longer.
Any idea what I'm doing wrong, or how I can replicate the old behavior?
Thanks!

Apparently this was resolved at some point before sbt 1.1.6.

Related

How to deploy symfony rest api project in hosting without third-party applications?

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.

Firebase and Unity: Unable to find command line tool error

After following tutorials on how to correctly install firebase into unity for an authentication system, I encountered an error that was:
Unable to find command line tool C:\The E-Learning System\Assets\Firebase\Editor\generate_xml_from_google_services_json.py required for Firebase Android resource generation.
From understnading it can not find either the google services file I imported into the assets folder or it could not find the generate_xml_from_google_services_json.py file. I looked online for people with similar problems could not find a clear answer to fix this.
This is a tool that ships with the SDK to support debugging your game in the Unity Editor. One minor caveat is that an exe actually ships on Windows (I assume that this is your operating system from the C:/). You should make sure that generate_xml_from_google_services_json.exe exists in that same directory (.exe's are typically ignored in many standard .gitignore as a catchall for build files). If it's missing, you can simply re-add the Firebase SDK and double check that this file gets included in your source repository.
If both generate_xml_from_google_services_json.py and generate_xml_from_google_services_json.exe exist under Assets/Firebase/Editor, you may also want to install Python for Windows (especially if you're still running Windows 7 or 8). This is due to a recent patch (as of 6.10.0) that fixes some incompatibilities with generate_xml_from_google_services_json.exe and older Windows variants. If that doesn't help, it would be awesome if you could file an issue or reach out to support directly. If there's a bug in that fallback, it would be helpful to surface that ASAP.
Let me know if that helps!
--Patrick

Meteor: what are the best settings in a production environment?

I am developing a meteor application. I noticed that the meteor server sometimes suddently crashes, this makes me think that it might not be optimized for production.
In a production environment, should I consider to add/remove some packages? Which one? And what are the best settings? I just want to make sure to have a reliable server that stay up all the time.
Have you taken a look at meteor up yet? It will set up a production quality server for you. I've used it for several production applications and it works great.
As far as adding/removing packages goes, I've never ran into any problems with installed packages running on production. A couple of my apps have about a dozen or so packages installed. But if you suspect that a package might be causing the problem, I would go to atmosphere and search for your packages and make sure that they haven't been flagged. You'll see a bright red flag next to the package name if it's been flagged by the community as "not working".
Maybe also check for issues on GitHub.
If you do decide to use meteor up, after your app has been uploaded to the server, you can check the log s for any problems.
mup logs -f

Version maintenance of artifacts in artifactory, when we do bug fixing in various environments

We use artifactory as a repo manager. We store packages for releases in repo libs-release-local and snapshot packages in libs-snapshot-local.
For example: If we send the war (web app) into test, it should be from libs-snapshot-local and if it is into stage & prod it will be from libs-release-local.
I will say a scenario, where I needed help below:
Once the war is certified good on test server we would send the same code to stage.
We saw a bug after deployed into stage, so we changed the code and again build it, it obviously cannot go to same versioned release(as in artifactory, we cannot override releases).
So,
What will happen if we recognized 10 bug fixes one at a time, after each deployment in stage ?
What if we have realized there are bug fixes after going to prod.
Artifactory will have bulk of folders with so many version names & folders. Is that good practice? Or else anything senses wrong in our procedure?
Thanks!
Suggest to read Binary repository management Refcard first.
You need define your strategy for your folders and wars (web application), it is already good to use different repo for different purpose (snapshot/release)
The process for maintenance is simple
fix the bug and increase the version, send to the libs-snapshot-local for testing
after testing, a.k.a QA passed, the packages are promoted to release/stage repo libs-release-local again for public use again.
In this case, bug fix is the same as normal development procedure.
or you can refine the questions to make your questions more clear.

Updating Symfony 2.0.9 the right way

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

Resources