Using Cloud SDK

Clase 22 de 54 • Full Stack JavaScript with Sails.js

Comentarios

Sami Perälahti

student•

So where are the mockups?

Michael Pacey

student•

I think it's just a case of going to https://ration.io and looking at what happens there.

Hussain Khan

student•

Hello, I'm having trouble with cloudsdk, getting unexpected identifier Cloud. destroy-one-thing works fine directly from browser console.

Also loading of available-things-page.js is before that of cloudjs.

Have gone through as per video, Please help to know what is causing this. Error Screen Shot attached .

Thanks

Hussain Khan

student•

Unfortunately I was missing async keyword in function definition. Now Things are working fine. Thanks

Thomas LaChacne

student•

function in js

Saad Khan Malik

student•

there is an error in the title of this video in the panel off screen,
it should be “Using Cloud SDK” and not “Using Cloud STK”,

Diego Forero

Team Platzi•

Thanks, the title was corrected

Loic Ducatillon

student•

In this tutorial, Cloud is used with await. I am looking how to get some kind of feedback from Cloud function. I cannot found any method such has .done( ) used in ajax. Anyone has some idea ? Thanks

Noitidart Saab

student•

I think this video when doesn’t have the latest changes. My git diff shows after rebuild there is ,"destoryOneThing":{"verb":"DELETE","url":"/api/v1/things/destory-one-thing","args":[]}. Notice the ,"args":[], I would thing “id” should be in the args. This is not explained. May you please add this to the video?

Jeff Baldwin

student•

I think you may have done something wrong as my args has an id attribute. Are you sure you added an id attribute to inputs on destroy-one-thing.js ?

Noitidart Saab

student•

Thanks @Jeffbaldwinjr you are right, I tried again after fixing the inputs and it is now populated.

Darius

student•

ok. I was apparentlyusing the wrong console. browser console works correctly. however, i still have to manually refresh to see the deleted records removed from the view…

Christopher Michael Reece

student•

You might need to add return exits.success(); to your destroy-one-thing.js action.

Mike USA

student•

If you mean you have to refresh your browser after you run the Cloud.command from the browser console, yes that is the expected behavior. That is what Mike was showing when he mentioned the browser view hadn't changed and then showed that the data no longer existed in the sails console, then went back to refresh the browser to show it was really updated. The Cloud.command is not immediately reflective in the view because no DOM update event was called.

Krzysztof Jabłoński

student•

Can I use Cloud SDK with waterline metod for example: User.find()?

Christopher Michael Reece

student•

It would’ve been cool to have a ship model in the background for the video recording. ()

Christopher Michael Reece

student•

“Thing” was deleted but no log out to the console. Maybe because I was in sails console?

Christopher Michael Reece

student•

Looks like I needed to return exits.success(); in my destroy-one-thing.js action.

Andrey Esaulov

student•

I get the 'await is only valid in async function’ error while trying to run

await Cloud.destroyOneThing.with({ id: thingId });

Andrey Esaulov

student•

No, await defenetly doesn’t work for me (and for eslinter). I could only make it work with .log() function:

    clickThing: function(thingId) {
      console.log('click thing #' + thingId);

      Cloud.destroyOneThing.with({ id: thingId }).log();
      _.remove(this.things, { id: thingId });
      this.$forceUpdate();
    }

Andrey Esaulov

student•

OK, found my error. Actually the clickThing should be async in order for await to work:

clickThing: async function(thingId) {
      console.log('click thing #' + thingId);

      await Cloud.destroyOneThing.with({ id: thingId });
      _.remove(this.things, { id: thingId });
      this.$forceUpdate();
    }```

yongun

student•

any one help me.

HP-ENVY-Notebook:~/demo/template_sailsjs$ sails run scripts/rebuild-cloud-sdk
info: Initializing hook... (`api/hooks/custom`)
 info: Initializing `apianalytics` hook...  (requests to monitored routes will be logged!)
debug: Initializing custom hook (`uploads`)
 info: ·• Auto-migrating...  (alter)
 info:    Hold tight, this could take a moment.
 info:  ✓ Auto-migration complete.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
WARNING: A function that was initially called over 15 seconds
ago has still not actually been executed.  Any chance the
source code is missing an "await"?

To assist you in hunting this down, here is a stack trace:

at whelk (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/node_modules/whelk/lib/whelk.js:620:18)
at Command.module.exports (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/bin/sails-run.js:244:7)
at Command.listener (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/node_modules/commander/index.js:300:8)
at Command.emit (events.js:160:13)
at Command.parseArgs (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/node_modules/commander/index.js:635:12)
at Command.parse (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/node_modules/commander/index.js:457:21)
at Object.<anonymous> (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/bin/sails.js:210:9)
at Module._compile (module.js:660:30)
at Object.Module._extensions..js (module.js:671:10)
at Module.load (module.js:573:32)
at tryModuleLoad (module.js:513:12)
at Function.Module._load (module.js:505:3)
at Function.Module.runMain (module.js:701:10)
at startup (bootstrap_node.js:190:16)
at bootstrap_node.js:662:3


 [?] For more help, visit https://sailsjs.com/support
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Could not run script, because the app could not be loaded.
 { Error: Sails is taking too long to load.

--  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --
 Troubleshooting tips:
  -• Were you still reading/responding to an interactive prompt?
     (Whoops, sorry!  Please lift again and try to respond a bit more quickly.)

  -• Do you have a lot of stuff in `assets/`?  Grunt might still be running.
    (Try increasing the hook timeout.  Currently it is 40000.
     e.g. `sails lift --hookTimeout=80000`)

  -• Is `custom` a custom or 3rd party hook?
    (Make sure its `initialize()` function triggers its callback.)
--  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --

    at Timeout.tooLong [as _onTimeout] (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/lib/app/private/loadHooks.js:191:21)
    at ontimeout (timers.js:458:11)
    at tryOnTimeout (timers.js:296:5)
    at Timer.listOnTimeout (timers.js:259:5) code: 'E_HOOK_TIMEOUT' }

Rory Silva

student•

I have this same issue. Did you ever resolve it?

Rory Silva

student•

I'm having the same problem as @yongun (6 months ago). The 'sails run rebuild-cloud-sdk' is stopping after the migration. I tried Node 9 and 10. 'sails lift' works but it gives me an ajax form error when I submit because there is no Cloud SDK. Help, please!

Rory Silva

student•

I changed to migrate: 'safe' and now I get: debug: Initializing custom hook (uploads) when trying to rebuild. Any clues?

William Alexander

student•

After adding the below line,

await Cloud.destroyOneThing.with({ id: thingId });

I get the following error:

Parsing error: Unexpected token Cloud (Fatal)

William Alexander

student•

Ok. This error was resolved after changing the clickThing to async function.

clickThing:  function(thingId) {

Changed to

clickThing: async function(thingId) {

Darius

student•

Getting the following error here: ReferenceError: Cloud is not defined

anyone seeing that?

Philippe Jeanneret

student•

You have to user the browser console. Not the terminal console.

Nima Soufiloo

student•

Is there any way to use cloud sdk in a standalone vuejs app ?

    clickThing: function(thingId) {
      console.log('click thing #' + thingId);

      Cloud.destroyOneThing.with({ id: thingId }).log();
      _.remove(this.things, { id: thingId });
      this.$forceUpdate();
    }

clickThing: async function(thingId) {
      console.log('click thing #' + thingId);

      await Cloud.destroyOneThing.with({ id: thingId });
      _.remove(this.things, { id: thingId });
      this.$forceUpdate();
    }```

HP-ENVY-Notebook:~/demo/template_sailsjs$ sails run scripts/rebuild-cloud-sdk
info: Initializing hook... (`api/hooks/custom`)
 info: Initializing `apianalytics` hook...  (requests to monitored routes will be logged!)
debug: Initializing custom hook (`uploads`)
 info: ·• Auto-migrating...  (alter)
 info:    Hold tight, this could take a moment.
 info:  ✓ Auto-migration complete.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
WARNING: A function that was initially called over 15 seconds
ago has still not actually been executed.  Any chance the
source code is missing an "await"?

To assist you in hunting this down, here is a stack trace:

at whelk (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/node_modules/whelk/lib/whelk.js:620:18)
at Command.module.exports (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/bin/sails-run.js:244:7)
at Command.listener (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/node_modules/commander/index.js:300:8)
at Command.emit (events.js:160:13)
at Command.parseArgs (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/node_modules/commander/index.js:635:12)
at Command.parse (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/node_modules/commander/index.js:457:21)
at Object.<anonymous> (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/bin/sails.js:210:9)
at Module._compile (module.js:660:30)
at Object.Module._extensions..js (module.js:671:10)
at Module.load (module.js:573:32)
at tryModuleLoad (module.js:513:12)
at Function.Module._load (module.js:505:3)
at Function.Module.runMain (module.js:701:10)
at startup (bootstrap_node.js:190:16)
at bootstrap_node.js:662:3

 [?] For more help, visit https://sailsjs.com/support
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Could not run script, because the app could not be loaded.
 { Error: Sails is taking too long to load.

--  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --
 Troubleshooting tips:
  -• Were you still reading/responding to an interactive prompt?
     (Whoops, sorry!  Please lift again and try to respond a bit more quickly.)

  -• Do you have a lot of stuff in `assets/`?  Grunt might still be running.
    (Try increasing the hook timeout.  Currently it is 40000.
     e.g. `sails lift --hookTimeout=80000`)

  -• Is `custom` a custom or 3rd party hook?
    (Make sure its `initialize()` function triggers its callback.)
--  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --

    at Timeout.tooLong [as _onTimeout] (/home/yongun/.nvm/versions/node/v9.5.0/lib/node_modules/sails/lib/app/private/loadHooks.js:191:21)
    at ontimeout (timers.js:458:11)
    at tryOnTimeout (timers.js:296:5)
    at Timer.listOnTimeout (timers.js:259:5) code: 'E_HOOK_TIMEOUT' }

Using Cloud SDK

Welcome to the course

Introduction and generalities

The technologies we are going to use

What we will build

Avoiding mistakes in our code

Github for our project

Installing platforms and dependencies

The essentials

Backend architecture

Frontend Architecture

ParasailsJS

Authentication and login

User Subscription

Sessions and Data Base

Password recovery

Email verification

Contact form

Managing payment information

Creating a new page

Making our page interactive

Creating a new model

Automatic testing

Creating a new action

Using Cloud SDK

Creating custom made functions

Personalization

Permissions

Friends with associations

Advanced queries and .populate

Modals

Ajax forms

Loading and error states

Putting it all together

Uploading backend file

Uploading frontend files

Downloading files

Your turn

Growth and monetization

Building a paywall

Recurrent payment subscriptions

Notifications

Invitations (Existing Users)

Invitations (New Users)

Unclaimed Accounts

Going live

SailsJS and NodeJS Settings

Application secutiry

Cloudflare and SSL Certifications

Using a platform as a service

Deploy to Heroku

Settings to send to production

Adding variables to Heroku

Data Base Settings

Before launching

Course Closure

Bonus content

Server-side rendering with EJS

Designing your frontend with Bootstrap 4

Understanding datastores

'Pure' APIs