I’m working with a friend to make a web application using adonisjs. I have the front page done and it is looking pretty slick at localhost:3333.
I need my partner who joined the repository to be able to work on it as well. He cloned my repo after installing the necessities. When he tries to adonis serve --dev, it says he isn’t in an adonisjs app. He can’t use the new command because it says the folder has to be empty (and he already has the framework files from the cloning, right?). So, he can’t launch the server because his computer doesn’t recognize it as an adonisjs app. What should we do so it acknowledges his clone is one?
when installing adonis your partner needs to install adonis globally npm i -g #adonisjs/cli
Then, when you have adoniscli installed make sure you install such dependencies npm install
Now, you can go to the adonis folder and run the project adonis serve --dev
Related
My firebase hosting deployments have suddenly started failing both in my Github CI Workflows and from my local machine.
$ firebase deploy --only hosting
=== Deploying to '<project>'...
i deploying hosting
Error: Failed to list functions for <project>
The project in question does not have any functions, and only hosts a static site. Google searches for "Failed to list functions" turn up empty, it seems like not a common problem. The only leads I can find indicate some kind of network error.
I have updated my firebase-tools, logged out and in again to generate a new CI token, tried the process from my Github workflows and also manually from my machine, all to the same effect.
I can't find any information about this problem, except that the error seems to come from this part of the firebase-tools codebase:
https://github.com/firebase/firebase-tools/blob/c0f19a32845135108c75a1050024965cb1e3f52d/src/gcp/cloudfunctions.ts
My firebase tools version was 11.14.0. I changed that to 11.13.0. Installed this specific version through npm install -g firebase-tools#11.13.0. After that I could successfully deploy.
I came across the issue. using firebase-tools version 10.5 or upgrading it to blaze plan fixed my issue
I recently finished developing a Laravel 9 app, using wsl2 and sail, just like I was told in the Laravel documentation. Since it’s my first time deploying to live ever, I ran into some differences with local and production files such as .env, docker-compose.yml and Dockerfile.
I tried using guides and tutorials but I can’t seem to make sense as to how to make it work. I have a droplet with a non-root user with sudo privileges, since I used these two kind guides:
https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-20-04
https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-compose-on-ubuntu-20-04
after finishing with the installation, I tried to clone my app and run it like I do locally, and nothing happened. I realize I can’t use sail on the server, but what is the correct way to make it work?
All three local files (.env, docker-compose.yml and Dockerfile) were never edited.
use this repository docker-laravel
i have Php, Composer, and mariadb on it.
I'm trying to set a Local Development Server for Lightning Web Components according to this link but when I try to install the plugin #salesforce/lwc-dev-server I get this error message :
Code: ShellParseError
and a .js file named npm-cli.js opens in my editor with this content:
#!/usr/bin/env node
require('../lib/cli.js')(process)
Anyone knows what to do? Thanks in advance.
In general, the local development for Lightning Web Components still has beta status: Local Development (Beta)
However, even the beta version can now be used relatively reliably. To set up local development you only need to authorize an org and install the development server. This allows you to develop locally without the need to push your components to an org first.
The local development server and its configuration are provided by a Salesforce CLI plugin. Before you install the plugin make sure you are using the latest Salesforce CLI version by running:
sfdx update
Then the lwc-dev-server plugin can be installed as follows:
sfdx plugins:install #salesforce/lwc-dev-server
After installing the plugin, to start the server on http://localhost:3333 and access all components of the project just run:
sfdx force:lightning:lwc:start
There is even a short official guide on how to set it up: Set Up LWC Local Development
I'm trying to deploy a Treeline app on my Ubuntu/Digital Ocean server with no luck.
I have worked successfully with sails (using "forever") before and tried to install treeline the same way.
npm install treeline -g
But after the installation, when trying to do something else, it always returns:
treeline.py: cannot connect to X server
I don't know if this error is due to my lack of experience deploying node or the earlier stage of the treeline project (which, on the other hand, is really awesome).
Thank you in advance.
Deploying a Treeline app is exactly the same as deploying a Sails app, because the files that get synched down from the Treeline server are Sails apps--they were just generated for you instead of you having to write the code. You don't need to npm install treeline -g on your server; that's only for previewing your app locally as you make changes to it on treeline.io. Instead, when you're ready to deploy, just follow whatever procedure that worked for your previous Sails apps and it will work for your Treeline app.
As far as the treeline.py error--that appears to be coming from a conflicting file pre-installed on Ubuntu!
I need to install features from update site when my product is launched and certain criteria is met. I read up on provisioning p2 repository and using API to install IU from there. I also found DirectorApplication for director and got pretty far with it, basically:
DirectorApplication app = new DirectorApplication();
String[] args = new String[]{"-repository", "http://myRepo","-installIU", "myFeature.feature.feature.group", "-destination", "myDestination"};
app.run(args);
myFeature is being installed but is running into some issues with missing dependency plugins. I am running this code from source and installing into finished product, so perhaps something is wrong there.
My main question so far is am I on the right track? Should I be using DirectorApplicaton directly (I know about implications of using internal packages) or provisioning my update site into p2 repository and follow this documentation? If it's the latter, is there more involved documentation?
I wouldn't use the DirectorApplication to install into the running Eclipse - AFAIK it is not meant for this. Instead, you should rather use the p2 API to manipulate the currently running installation.