I am working with a new client, but it seems I can't find the Amplify Graphql API in the amplify folder. I used to see the folder when working with Amplify but in this case, after pulling the environment I can't see the folder.
amplify status
terminal output
amplify folder structure
terminal output
Related
I accidentally deleted my amplify frontend and created a new one. How do I import the existing amplify back end to the newly created amplify app project folder?
I followed the steps on the backend tab
amplify init --appId ("ID OF YOUR NEW AMPLIFY APP").
Instead of amplify add CATEGORY here. I use amplify update CATEGORY here
Then amplify push.
But when I check the amplify app on the AWS console there still no backend integrated to it.
Am I doing correct?
Version used:
"aws-amplify": "^2.1.0"
you can use the following command:
amplify pull --appId someidgoeshere --envName dev
I have 2 hosting in my project. I need to upload my application in other hosting. But in project lists its not showing other hosting option.
Steps i follow
npm install -g firebase-tools
firebase login
firebase init
then i select the project
and firebase deploy
but need to upload on second hosting
It sounds like you are working with two different projects. If you access those projects with the same Google account, you can add a second project to your local configuration with the firebase use --add command, as described in the documentation:
Add a project alias
When you select a Firebase project during project initialization, the
project is automatically assigned the alias of default. However, to
allow project-specific commands to run against a different Firebase
project but still use the same project directory, run the following
command from within your project directory:
firebase use --add
This command prompts you to select another Firebase project and assign
the project as alias. Alias assignments are written to a .firebaserc
file inside your project directory.
Then you can use that alias to switch projects.
firebase use project_id_or_alias Directs all commands to run against the specified Firebase project. The CLI uses this project as the currently "active project".
Read more of the documentation for more details.
If you have to use different Google accounts for each project, you will have to log out and log back in with the CLI each time you want to change.
You can change your project using this command firebase use <project_id>
and you can set your default project in .firebaserc
{
"projects": {
"default": "<project_name>"
}
}
You are looking for this
firebase target:apply hosting target-name resource-name
Read more Here
For logging purposes I´d like to print to console or even display the current deploy ID (or message) of my firebase web app that is being accessed by the browser.
Firebase Hosting recently released a new REST API. You can use sites.releases.list to see what version is currently deployed.
Old answer:
Firebase deploy IDs don't appear to be available anywhere via programmatic access. The CLI doesn't support listing current or previous deploys.
My recommendation would be to go in the other direction. Have your source code in a vcs like git. When you build and deploy a new version set the vcs hash or version in the deployed code and as the message for firebase deploy. You can then log the log the source version in your code and you can manually associate that back to a release in the Firebase UI.
I want to try the demo for polymerfire in firebase. To get it run locally I followed these steps. But what exact steps do I need to do to get it to run in firebase?
I figured firebase init and firebase deploy should be run but the browser only displays errors in the console. Must the polymer project be build in a certain way and what should the firebase "public" folder be?
All files from public folder will be deployed to your Firebase static web hosting, so you can access them though your Firebase hosting address like https://projectname-5gek53.firebaseapp.com/. This allows you to upload your web app.
You build your polymer app (I guess you need to run polymer build). You drag all files generated as production build to your public folder. Next, you run firebase deploy and after deployment process your app will be accessible from your hosting address as I mentioned above.
Edit: Polymerfire demo is actually not that simple to export, but I found a really nice tutorial step-by-step from Google Codelabs here is a link Build a Progressive Web App with Firebase, Polymerfire and Polymer Components
I just installed a new version of the polymer cli and Firebase cli. When I do a Polymer build, no build/bundled or build/unbundled is created.
I do get a build/default, which I can run with a firebase serve and a firebase deploy. So something has changed recently. just fyi
What is the proper way to deploy webapps on Heroku? I'm installing Moodle, but the same procedure should apply to e.g. Drupal or Wordpress. What I hace done is to unzip Moodle locally, then uploaded it using git to Heroku. When I then visit my site I get the option to install it and select the database, which works fine. The problem is that the install procedure saves information in the filesystem on the server, which gets overwritten next time I deploy my app. So what is the proper way of doing this?
You have to pre-configure your app with all of the database settings before you deploy to Heroku. So either do a fake "install" on your local environment, or manually edit your php config files.
As you've discovered, Heroku's filesystem is not persistent: https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem.