I am trying to get this app to work on my laptop. I am using npm start to start the application but it gives me errors. How do I get it to start? This is the code I am using. It is a clone of an app on GitHub.
https://github.com/adrianhajdin/project_medical_pager_chat.git
From your comment, you're not running npm install in the right directory.
There is a client and a server folder. You need to npm install in both, and run both.
Download the ZIP file and extract
Go into the server folder and run npm install && npm start
Go into the client folder and run npm install && npm start
This will cause http://localhost:3000/ to open in your default browser which is the client application, which apparently connects to the server application.
Note: I had to change the server port from 5000 to 5001 for some reason. That change can be made in server/index.js. You may not have this probem.
Related
I have been making lots of changes in appearance source code (variables.less => static/assets/variables.less) of superset and then did a superset init but nothing changed. Do we have to do something else to reconfigure those changes?
Superset init creates default roles and permissions, so it's a backend task! When you want to customize superset you should run backend and frontend separately as per official instructions.
Then in a terminal you should have a tab for the backend, and another for the frontend. When changing the frontend's code you'll have to run npm install inside the superset-frontend directory once, and to run it you will have to run the command npm run dev-server.
All these steps are documented in the link I provided though. I recommend re-reading the documentation.
I believe you need to rebuild the assets:
cd into the /assets directory; then
$ npm install
$ npm install webpack
$ npm run prod
If this doesn't work, try https://github.com/apache/incubator-superset/blob/master/CONTRIBUTING.md#frontend-assets
I've been using DDEV & Docker-Desktop sucessfully to run installs of drupal8 on my windows 10 machine.
Today I decided to create a new install of Drupal8 (I last did this a month ago or so).
I followed the basic steps:
Create new folder (drupal8test)
Ran the ddev config command inside this folder.
accepted the defaults and choose drupal8
Amended config.yaml so the ports do not clash with others on my machine
Ran the command ddev start
I get a couple of alerts from docker desktop and I share folder's it needs
There are no errors and the URL is provided, on going there I get a 404 file cannot be found error
When I look in the drupal8test folder I see the following folders:
.ddev
drush
files
sites
(Expecting to see web).
Any ideas? (I'm quite new to Drupal and DDEV so I'm sure I'm doing something wrong)
Welcome to ddev and to Drupal, Mark!
ddev has never installed Drupal, it's a local development environment.
There are quickstarts for Drupal (all versions), TYPO3, Magento and Magento2, etc at https://ddev.readthedocs.io/en/stable/users/cli-usage/#quickstart-guides
For Drupal 8, you would follow the Drupal 8 Quickstart:
mkdir my-drupal8-site
cd my-drupal8-site
ddev config --project-type=drupal8 --docroot=web --create-docroot
ddev start
ddev composer create "drupal/recommended-project:^8"
ddev composer require drush/drush
ddev launch
I'm not sure I understand the command you showed
.ddev drush files sites
or what it was trying to accomplish, but after doing this install you can just ls and you'll see the web directory. If you're interested in running drush, you can ddev exec drush status for example, or just ddev ssh and use drush.
Anyway, the next time you get stuck, the docs are waiting for you at https://ddev.readthedocs.io/en/stable/ and there is also lots of community support available here and elsewhere.
I am trying to update files on a project that already has been deployed. The changes are not taking place when seeing it deployed, though when I sudo vim these files via GitBash, it shows the changes. Here's how I did when I'm logged into the server Ubuntu via AWS.
cd into the project
git add .
git commit -a -m "message"
git pull origin master
(it comes out a Nano screen--so I input a message then Ctrl X and then respond "no") and it shows the changes through vim.
There's no changes when I refresh the deployed project, and not even when I reboot it via AWS. Can someone please share the steps to make changes and show changes on a deployed project? Thank you so much, I appreciate your feedback!
You need to restart the service running your app to update the app:
sudo systemctl restart service_name
The apt-buildpack is experimental and not yet intended for production use. I guess that's why also no documentation.
Creating container
Successfully created container
Downloading app package...
Downloaded app package (862.7K)
Warning: this buildpack can only be run as a supply buildpack, it can not be run alone
Failed to compile droplet: Failed to compile droplet: exit status 1
Destroying container
Exit status 223
Stopping instance abdfc8d0-699e-4834-9f2d-2b8aec218423
Successfully destroyed container
Can you give me example how to push cf-env sample app and install for example rtorrent and/or openvpn. Is it possible to install gnome for testing purposes?
As far as usage goes it's pretty simple, you just need to include an apt.yml in the root directory of your app. That should contain among other things, the list of packages to install.
Ex:
---
packages:
- ascii
- libxml
- https://example.com/exciting.deb
The buildpack supports installing package names, deb files, custom APT repositories, and even PPAs.
Please see the README for further instructions.
This message:
Warning: this buildpack can only be run as a supply buildpack, it can not be run alone
Is telling you that the Apt buildpack only functions to supply binaries. It doesn't actually know how to run your app or any application. For more on the supply script, check out the docs here.
The trick to making it work is that you need to use multi buildpack support. Instructions for doing that can be found here. This should work with most apps, but there's a simple example here.
Once your app stages & starts, you can confirm that your packages were installed by running cf ssh apt-test -t -c "/tmp/lifecycle/launcher /home/vcap/app bash ''". Anything that was installed should be on the path, but if you want to see where things are installed it'll be under the /home/vcap/deps/<buildpack-number>/.
That should be about it. Hope that helps!
I have installed browser sync with npm. On their website, they have mentioned that it also allows remote debugging. But they have not mentioned that how to do remote debugging.
I have used below command to run mysite on browser-sync.
browser-sync start --proxy localhost:8080/mysite
how can I remote debug that?
Though this was quite a tricky process in versions before Browser-sync 2.0, but with Browser-sync 2.0 you now have a brand new Web UI, which makes this process a whole lot easier.
Firstly you need to update Browser-sync to it's latest version
npm install -g browser-sync#latest
Then run any command like you would.
eg:
browser-sync start --proxy "myproject.dev" --files "css/*.css"
To open this Web UI open
http://localhost:3001
Below are links to articles that talk about Remote Debuggging in Browser-Sync:
http://www.wearejh.com/news/browsersync-2-0/
http://www.sitepoint.com/improve-workflow-browsersync-2-0/