Julian Bez webjunkie

Python relative imports in AWS Lambda fail with attempted relative import with no known parent package

The Problem

In AWS Lambda if I attempt an explicit relative import like this

.
├── lambda_file.py
└── example.py

How we incorporate next and cloudfront (2018-04-21)

Feel free to contact me at [email protected] or tweet at me @statisticsftw

This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!

It assumes some knowledge of AWS.

Goals

In order to run this image do: docker-compose up -d to get all up. On first run DB initialization and initial user setup is done like so:

First start a bash in the container: docker-compose exec sentry /bin/bash. Then, inside bash, do sentry upgrade wait until it asks you for an inital user. When finished exit the bash.

When in doubt check with docker-compose ps if all went fine.

	Description: Generic AWS VPC Networking
	Parameters:
	PrivateToInternetAccess:
	Type: String
	Description: If true, NAT Gateways and Elastic IPs will be created for the internet access from private subnets.
	AllowedValues:
	- "false"
	- "true"
	Default: "false"
	CidrPrefix:

	from django.http import HttpResponse

	PIXEL_GIF_DATA = """
	R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
	""".strip().decode('base64')

	def pixel_gif(request):
	return HttpResponse(PIXEL_GIF_DATA, content_type='image/gif')

	" vim:fdm=marker
	"
	" =============================================================================
	" vim-plug {{{
	" =============================================================================

	call plug#begin('~/.vim/bundle')

	function! BuildYCM(info)
	" info is a dictionary with 3 fields

Julian Bez webjunkie

The Problem

How we incorporate next and cloudfront (2018-04-21)

Goals

Default

Powerlevel10k