Python relative imports in AWS Lambda fail with attempted relative import with no known parent package
In AWS Lambda if I attempt an explicit relative import like this
.
├── lambda_file.py
└── example.py
| # Copyright (c) 2018 Bao Nguyen <[email protected]> | |
| # | |
| # Permission is hereby granted, free of charge, to any person obtaining a copy | |
| # of this software and associated documentation files (the "Software"), to deal | |
| # in the Software without restriction, including without limitation the rights | |
| # to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| # copies of the Software, and to permit persons to whom the Software is | |
| # furnished to do so, subject to the following conditions: | |
| # | |
| # The above copyright notice and this permission notice shall be included in all |
| if Vagrant.has_plugin?('vagrant-exec') | |
| config.exec.commands '*', directory: '/var/www/drupal' | |
| end | |
| <?php | |
| $filesystem = \Drupal::service('file_system'); | |
| // Create file entity. | |
| $image = File::create(); | |
| $image->setFileUri($destination); | |
| $image->setOwnerId(\Drupal::currentUser()->id()); | |
| $image->setMimeType('image/' . pathinfo($destination, PATHINFO_EXTENSION)); | |
| $image->setFileName($filesystem->basename($destination)); | |
| $image->setPermanent(); | |
| $image->save(); |
| // Create a Promise that resolves after ms time | |
| var timer = function(ms) { | |
| return new Promise(resolve => { | |
| setTimeout(resolve, ms); | |
| }); | |
| }; | |
| // Repeatedly generate a number starting | |
| // from 0 after a random amount of time | |
| var source = async function*() { |
A curated list of AWS resources to prepare for the AWS Certifications
A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.
This gist contains lists of modules available in
in AWS Lambda.
| var fs = require('fs'); | |
| var Q = require('q'); | |
| var spawn = require('child_process').spawn; | |
| var path = require('path'); | |
| // Make sure you append the path with the lambda deployment path, so you can | |
| // execute your own binaries in, say, bin/ | |
| process.env["PATH"] = process.env["PATH"] + ":" + process.env["LAMBDA_TASK_ROOT"] + '/bin/'; | |
| function spawnCmd(cmd, args, opts) { |
This assumes you are now connected to the server via SSH.
sudo -s Enter root mode for admin accessgroupadd devgroup Create new group to be later granted access to /var/www/htmluseradd -G root,devgroup masterdev Create new root user. Also add to the devgrouppasswd masterdev Change password for the new root user