Chris Harland cwharland

## Palworld-Server-FAQ-Community.md

      
              1 file
            
          
              2 forks
            
          
              40 comments
            
          
              74 stars
            
          
                Toakan
                / Palworld-Server-FAQ-Community.md
            
            
              Last active
              March 20, 2024 07:23
            
              
                Palworld Server Community FAQ
              
          
    Palworld Server Community FAQ

I've been in the #pal-server-help channel for a while now, and these same things keep coming up. So here's a one stop list of items people keep asking for.
Server Setup

Server Recommended Specs (For 8-12 Players)


4x CPU cores @3.8Ghz+
30GB Storage
8GB RAM Base + 2GB RAM per player (If using scheduled restarts)


## 00 - pw - saves.md

      
              3 files
            
          
              2 forks
            
          
              0 comments
            
          
              16 stars
            
          
                arawrshi
                / 00 - pw - saves.md
            
            
              Last active
              January 29, 2024 16:34
            
              
                Palworld - Convert saves to json and back
              
          
Download https://github.com/trumank/uesave-rs & https://gist.github.com/cheahjs/300239464dd84fe6902893b6b9250fd0
In your terminal run python convert-to-json.py <path-to-uesave.exe> <path-to-savefile-folder>


eg python convert-to-json.py uesave.exe Pal/Saved/SavedGames/steamid/saveid

Source: Palworld Discord
Attached gist as of timestamp.

  
## index.html
<!DOCTYPE html>
<html>
  <head>
    <meta charset="UTF-8" />
    <title>Add React in One Minute</title>
  </head>
  <body>

    <h2>Add React in One Minute</h2>
    <p>This page demonstrates using React with no build tooling.</p>

## weird-lambda-binaries-recipe.md

      
              1 file
            
          
              1 fork
            
          
              4 comments
            
          
              16 stars
            
          
                smithclay
                / weird-lambda-binaries-recipe.md
            
            
              Created
              July 28, 2017 02:59
            
              
                Recipe for Getting Strange Binaries Running in AWS Lambda
              
          
    Recipe for running strange binaries in AWS Lambda

In general, the command ldd and the environment variable LD_LINKER_PATH is your best friend when running new, untested binaries in Lambda. My process (which I want to get around to automating one day, maybe using Packer), goes like this:

Run an EC2 instance with the official AWS Lambda AMI.
Get binary you want to run in AWS Lambda running on the instance (either by installing from a package manager or compiling). 
Run ldd -v ./the-binary. Note all of the shared libraries it requires. You’ll need to remember these.
Copy the binary to your local machine. Upload the binary with your AWS Lambda function code that runs the ldd command inside the handler function using the process execution library from your language of choice. In node, this works just fine: console.log(require('child_process').execSync('ldd -v ./the-binary'))
Note any shared libraries that are missing in the function output. Copy those over from the EC2 instance to a direct


## twitter_oauth_user_context.js
const OAuth = require('oauth');
const Twit = require('twit');
const nconf = require('nconf');

// temp global var
var oAuthTokenSecret;

// load config file which contains twitter app tokens
nconf.file({ file: './config/twitter-share.json' }).env()

## how-to-make-a-racist-ai-without-really-trying.ipynb

      
              1 file
            
          
              38 forks
            
          
              9 comments
            
          
              228 stars
            
          
                rspeer
                / how-to-make-a-racist-ai-without-really-trying.ipynb
            
            
              Last active
              December 23, 2023 22:54
            
          
      Sorry, something went wrong. Reload?
      Sorry, we cannot display this file.
      Sorry, this file is invalid so it cannot be displayed.
      
          Viewer requires iframe.
      
    
## lambda.py
# Run get info from Elasticsearch  from AWS Lambda.
from __future__ import print_function

import boto3
import certifi
import yaml
from aws_requests_auth.aws_auth import AWSRequestsAuth
from elasticsearch import Elasticsearch, RequestsHttpConnection

def handler(event, context):

## test_dags.py
import os
import unittest

from airflow.models import DagBag

class TestDags(unittest.TestCase):
    """
    Generic tests that all DAGs in the repository should be able to pass.
    """

## airflow-supervisord.conf
; Configuration for Airflow webserver and scheduler in Supervisor

[program:airflow]
command=/bin/airflow webserver
stopsignal=QUIT
stopasgroup=true
user=airflow
stdout_logfile=/var/log/airflow/airflow-stdout.log
stderr_logfile=/var/log/airflow/airflow-stderr.log
environment=HOME="/home/airflow",AIRFLOW_HOME="/etc/airflow",TMPDIR="/storage/airflow_tmp"

## Makefile
# Example makefile with some dummy rules

.PHONY: all
## Make ALL the things; this includes: building the target, testing it, and
## deploying to server.
all: test deploy

.PHONY: build
# No documentation; target will be omitted from help display
build:
	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="UTF-8" />
	<title>Add React in One Minute</title>
	</head>
	<body>

	<h2>Add React in One Minute</h2>
	<p>This page demonstrates using React with no build tooling.</p>
	const OAuth = require('oauth');
	const Twit = require('twit');
	const nconf = require('nconf');

	// temp global var
	var oAuthTokenSecret;

	// load config file which contains twitter app tokens
	nconf.file({ file: './config/twitter-share.json' }).env()
	# Run get info from Elasticsearch from AWS Lambda.
	from __future__ import print_function

	import boto3
	import certifi
	import yaml
	from aws_requests_auth.aws_auth import AWSRequestsAuth
	from elasticsearch import Elasticsearch, RequestsHttpConnection

	def handler(event, context):
	import os
	import unittest

	from airflow.models import DagBag

	class TestDags(unittest.TestCase):
	"""
	Generic tests that all DAGs in the repository should be able to pass.
	"""
	; Configuration for Airflow webserver and scheduler in Supervisor

	[program:airflow]
	command=/bin/airflow webserver
	stopsignal=QUIT
	stopasgroup=true
	user=airflow
	stdout_logfile=/var/log/airflow/airflow-stdout.log
	stderr_logfile=/var/log/airflow/airflow-stderr.log
	environment=HOME="/home/airflow",AIRFLOW_HOME="/etc/airflow",TMPDIR="/storage/airflow_tmp"
	# Example makefile with some dummy rules

	.PHONY: all
	## Make ALL the things; this includes: building the target, testing it, and
	## deploying to server.
	all: test deploy

	.PHONY: build
	# No documentation; target will be omitted from help display
	build: