poliastro is a huge package and its size is exceeding zeit now limits

[emptymalei]

Thus limit of aws.

It definitely needs a work around.

---

It may not work with serverless. So I have to make this a local python module. Or I could deploy it on heroku.

[emptymalei]

After some investigation, I gave up on this.

There are two choices.

1. Use a light package and save auxiliary data in db.
2. Deploy it as a full app instead of serverless.

For this purpose, neither of the two is worth the effort.

This project will go on in another direction:

Create the real-time potential map in our solar system and design the game locally. I will design the local module API as independent as possible so we could plug or unplug it at any time.

[OpenSourceZombie]

I can help you with deploying it as a normal app

[emptymalei]

@OpenSourceZombie Like a full-fledged flask app on Heroku?

Here are some background.

I am creating this because I need this for another project called orbits in solar systems.
This orbits in solar systems project requires the positions of the planets. I could directly create a python module to get positions in this project but I might need astro positions API for the front end. So I am thinking that I should just directly create the API for the positions first.

Yeah, while I am writing, I convinced myself that I should deploy it as a full app. In the end, the orbit calculation part will also gonna be huge.

Correct me if I am wrong, I think I need to:

• rewrite it as a flask app
• prepare heroku configs
• deploy on heroku

[emptymalei]

@OpenSourceZombie I found the solution. I built a minified lambda layer for the libs I am using. It fits into aws lambda functions.
I just need to rewrite the code to serverless.